[jira] [Updated] (MESOS-833) The Status Update Manager should use a back-off mechanism for retried updates.

["Vinod Kone (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MESOS-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kone updated MESOS-833:
-----------------------------

    Fix Version/s: 0.16.0

> The Status Update Manager should use a back-off mechanism for retried updates.
> ------------------------------------------------------------------------------
>
>                 Key: MESOS-833
>                 URL: https://issues.apache.org/jira/browse/MESOS-833
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Benjamin Mahler
>            Assignee: Vinod Kone
>            Priority: Critical
>              Labels: reliability
>             Fix For: 0.16.0
>
>
> In the event of a delay receiving status update acknowledgements, all status update managers will begin re-sending status updates on a fixed 10 second interval. This can cause a large influx of duplicate status updates in the system, possibly overloading schedulers.
> The Status Update Manager should avoid compounding any status update backlog issues through a retry back-off mechanism. Possibly a truncated exponential back-off.



--
This message was sent by Atlassian JIRA
(v6.1#6144)