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

["Alexander Rukletsov (JIRA)" <ji...@apache.org>]

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

Alexander Rukletsov commented on MESOS-3157:
--------------------------------------------

I think having a master flag is fine for now, however, it would be nice to provide flags for the built-in allocator in a more general manner, without creating a master flag for each allocator option. I think this is what [~bmahler] suggests. On the other side, since custom allocators may have their own flags in the module description, it seems a bit weird to have two blobs of flags: custom and general, which may still be of no interest to custom allocators.

> 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)