So the best approach would be to write my own hierarchical allocator? As of now, I am currently filtering out offers made, but this adds latency because, the required resources may not be offered for every request.
On 31 May 2016 at 13:34, <[email protected]> wrote: > Just FYI, note the default hierarchical allocator doesn't do anything with > the resource requests it receives. See > https://github.com/apache/mesos/blob/master/src/master/allocator/mesos/hierarchical.cpp > > On May 30, 2016, at 23:58, Guangya Liu <[email protected]> wrote: > > I think that you can filter the offers based on slave attribute, all of > the offers are assigned agent attributes in the offer: > https://github.com/apache/mesos/blob/master/src/master/master.cpp#L5637 > > On Tue, May 31, 2016 at 2:33 PM, Nihal Harish <[email protected]> > wrote: > >> Hi, >> >> The mesos.proto file allows us to specify request offers based on only >> slave_id and resources, is there some way to request offers based on slave >> attributes and/or hostname? >> >> Thanks. >> Regards, >> Nihal >> >> >
