New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
notify-rate-limiter assumes apps, no pods #4863
Comments
I have a funny feeling we don't do this for scale checks, health checks, etc... definitely a blocker |
jasongilanfarr
pushed a commit
that referenced
this issue
Dec 20, 2016
Summary: The rate limiter incorrectly assumed that all runSpecs are apps. Test Plan: sbt test with new test Reviewers: meichstedt, jdef, timcharper, aquamatthias Reviewed By: jdef, timcharper, aquamatthias Subscribers: aquamatthias, jenkins, marathon-team Differential Revision: https://phabricator.mesosphere.com/D352
aquamatthias
pushed a commit
that referenced
this issue
Dec 21, 2016
Summary: The rate limiter incorrectly assumed that all runSpecs are apps. Test Plan: sbt test with new test Reviewers: meichstedt, jdef, timcharper, aquamatthias Reviewed By: jdef, timcharper, aquamatthias Subscribers: aquamatthias, jenkins, marathon-team Differential Revision: https://phabricator.mesosphere.com/D352 (cherry picked from commit c8924aa)
This was referenced Dec 21, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
rate limiting should work for BOTH apps and pods
xref
marathon/src/main/scala/mesosphere/marathon/core/task/update/impl/steps/NotifyRateLimiterStepImpl.scala
Line 36 in 0f13200
The text was updated successfully, but these errors were encountered: