[jira] [Commented] (MESOS-3157) only perform batch resource allocations

["James Peach (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057348#comment-15057348 ] 

James Peach commented on MESOS-3157:
------------------------------------

I'm working on a benchmark. I haven't been able to come up with a sequence of events that reproduces the problem. In general, when you get a sequence of full allocation passes, all the cluster resources get offered on the first pass so, while is is easy to get lots of passes queued up, the subsequent passes don't end up doing any work.

> only perform batch resource allocations
> ---------------------------------------
>
>                 Key: MESOS-3157
>                 URL: https://issues.apache.org/jira/browse/MESOS-3157
>             Project: Mesos
>          Issue Type: Bug
>          Components: allocation
>            Reporter: James Peach
>            Assignee: James Peach
>
> 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).
> We have been running a patch to remove all the event-triggered allocations and only allocate from the batch task {{HierarchicalAllocatorProcess::batch}}. This works great and really improves responsiveness.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)