Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Wed, 11 Nov 2015 04:57:10 +0000 (UTC)
From: "James Peach (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12849434.1438031135000.36396.1447217830940@Atlassian.JIRA>
In-Reply-To: <JIRA.12849434.1438031135000@Atlassian.JIRA>
References: <JIRA.12849434.1438031135000@Atlassian.JIRA>
 <JIRA.12849434.1438031135981@arcas>
Subject: [jira] [Commented] (MESOS-3157) only perform batch resource
 allocations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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