[
https://issues.apache.org/jira/browse/MESOS-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644889#comment-14644889
]
James Peach edited comment on MESOS-3157 at 7/28/15 7:26 PM:
-------------------------------------------------------------
There's definitely room for performance optimizations in the allocator (for
example MESOS-3075, MESOS-3052 and MESOS-3051), and I'll probably come back and
do some work on those issues. However, we would still need this option because
it decouples the cost of allocation from the amount of churn in the
environment. I'll knock up a patch and post for review (likely a couple of
weeks to get through internal review processes).
was (Author: jamespeach):
There's definitely room for performance optimizations in the allocator (for
example MESOS-3075, MESOS-3052 and MESOS-30510), and I'll probably come back
and do some work on those issues. However, we would still need this option
because it decouples the cost of allocation from the amount of churn in the
environment. I'll knock up a patch and post for review (likely a couple of
weeks to get through internal review processes).
> 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)
