Skip to content
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

When we copy liveness to readiness, liveness should have increased failure threshold #53

Open
mortenlj opened this issue Dec 2, 2019 · 0 comments

Comments

@mortenlj
Copy link
Member

mortenlj commented Dec 2, 2019

When a user only specifies a liveness check, our current behavior is to copy it to the readiness check.
Some blogs advocate that in the case where your liveness and readiness checks are the same, the liveness check should have a higher failure threshold.

This will allow your app to be considered unready and taken out of rotation, while still giving it some more tries to get ready before it is killed. This would help in cases where high load from the start makes it harder to come up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant