[ https://issues.apache.org/jira/browse/MESOS-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yan Xu updated MESOS-6904: -------------------------- Target Version/s: 1.2.0 [~adam-mesos] trying to land this in the next couple of days to get it into 1.2. Should it be a blocker? (It doesn't have to go in but it would be nice if we could) > Perform batching of allocations to reduce allocator queue backlogging. > ---------------------------------------------------------------------- > > Key: MESOS-6904 > URL: https://issues.apache.org/jira/browse/MESOS-6904 > Project: Mesos > Issue Type: Bug > Components: allocation > Reporter: Jacob Janco > Assignee: Jacob Janco > Labels: allocator > > Per MESOS-3157: > {quote} > Our deployment environments have a lot of churn, with many short-live > frameworks that often revive offers. Running the allocator takes a long time > (from seconds up to minutes). > In this situation, event-triggered allocation causes the event queue in the > allocator process to get very long, and the allocator effectively becomes > unresponsive (eg. a revive offers message takes too long to come to the head > of the queue). > {quote} > To remedy the above scenario, it is proposed to perform batching of the > enqueued allocation operations so that a single allocation operation can > satisfy N enqueued allocations. This should reduce the potential for > backlogging in the allocator. See the discussion > [here|https://issues.apache.org/jira/browse/MESOS-3157?focusedCommentId=14728377&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14728377] > in MESOS-3157. -- This message was sent by Atlassian JIRA (v6.3.4#6332)