mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yan Xu (JIRA)" <>
Subject [jira] [Commented] (MESOS-6904) Perform batching of allocations to reduce allocator queue backlogging.
Date Fri, 03 Feb 2017 23:58:51 GMT


Yan Xu commented on MESOS-6904:

Follow up fix:

commit f686f04f57b967dfe1cc2d3a5f09250812013d46
Author: Jacob Janco <>
Date:   Fri Feb 3 15:51:07 2017 -0800

    Fix to potential dangling pointer in `batch()`.
    - If `HierarchicalAllocatorProcess` is gone after
      `allocate` but before `AnyCallback` then
      `this->allocationInterval` may reference

> Perform batching of allocations to reduce allocator queue backlogging.
> ----------------------------------------------------------------------
>                 Key: MESOS-6904
>                 URL:
>             Project: Mesos
>          Issue Type: Bug
>          Components: allocation
>            Reporter: Jacob Janco
>            Assignee: Jacob Janco
>            Priority: Critical
>              Labels: allocator
>             Fix For: 1.2.0
> Per MESOS-3157:
> {quote}
> 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).
> {quote}
> To remedy the above scenario, it is proposed to perform batching of the enqueued allocation
operations so that a single allocation operation can satisfy N enqueued allocations. This
should reduce the potential for backlogging in the allocator. See the discussion [here|]
in MESOS-3157.

This message was sent by Atlassian JIRA

View raw message