mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Peach (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-3157) only perform batch resource allocations
Date Wed, 11 Nov 2015 04:57:10 GMT

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

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

No, I hope to get back to it soon though.

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

Mime
View raw message