HomeMesosphereNo notifications. 4 unresolved issues.

Do a better job at maintaining task failure rate limiting values per RunSpec
ClosedAll Users

Authored by ichernetsky on Aug 30 2017, 10:52 PM.



Use maxLaunchDelay to determine what delays to GC.

In addition to that, on conditions like Running, Created, existing delays are
advanced to make sure that delays are applied to failures, and time taken by
provisioning containers doesn't get subtracted from them.

In the future we might implement removal of rate-limiting delays when
a corresponding RunSpec becomes healthy.

This is a back-port from master branch.

Test Plan

sbt test

Diff Detail

rMARATHON marathon
No Linters Available
No Unit Test Coverage
Build Status
Buildable 3412
Build 6521: Marathon (revised)Jenkins
Build 6520: arc lint + arc unit
ichernetsky created this revision.Aug 30 2017, 10:52 PM
ichernetsky edited the summary of this revision. (Show Details)Aug 30 2017, 11:02 PM
timcharper accepted this revision.Sep 5 2017, 6:37 PM

Are you planning to note in the commit message that this is a back-port?

This revision is now accepted and ready to land.Sep 5 2017, 6:37 PM
ichernetsky edited the summary of this revision. (Show Details)Sep 5 2017, 6:45 PM
kensipe accepted this revision.Sep 5 2017, 7:42 PM

I thought our process was to put back ports on GH PRs and not on phabricator... otherwise lgtm

ichernetsky closed this revision.Sep 5 2017, 10:10 PM