You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2013/11/21 19:58:35 UTC

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

Benjamin Mahler created MESOS-833:
-------------------------------------

             Summary: 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
            Priority: Critical


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)