mesos-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrei Sekretenko <asekrete...@apache.org>
Subject Re: Review Request 72887: Tied the 1st hierarchical allocator process to a process ID "allocator".
Date Mon, 21 Sep 2020 12:43:25 GMT

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/72887/
-----------------------------------------------------------

(Updated Sept. 21, 2020, 2:43 p.m.)


Review request for mesos and Benjamin Mahler.


Changes
-------

Resorted to tying only the first process to `"allocator"`.


Summary (updated)
-----------------

Tied the 1st hierarchical allocator process to a process ID "allocator".


Bugs: MESOS-10177
    https://issues.apache.org/jira/browse/MESOS-10177


Repository: mesos


Description (updated)
-------

The instances of `HierarchicalAllocatorProcess` launched in the same
instance of libprocess after that will be assigned IDs like
"allocator(2)", "allocator(3)" and so on.

This allows the user to specify a fixed URL like
`https://localhost:5050/allocator/offer_constraints_debug` when querying
HTTP endpoints of an allocator in the mesos-master program instead of
looking up the allocator UPID and using that to compose an URL (like
`https://localhost:5050/hierarchical_allocator(1)/...`)


Diffs (updated)
-----

  src/master/allocator/mesos/hierarchical.hpp 225de160772fe689e07877c895800eb711f211b5 


Diff: https://reviews.apache.org/r/72887/diff/2/

Changes: https://reviews.apache.org/r/72887/diff/1-2/


Testing
-------

`make check` on several platforms + tested the debug endpoint manually


Thanks,

Andrei Sekretenko


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message