Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upTaking restart_delay into account when incrementing unstable_restarts #3990
Conversation
This comment has been minimized.
This comment has been minimized.
CLAassistant
commented
Oct 27, 2018
•
|
|
Unitech
force-pushed the
Unitech:development
branch
from
4ba9720
to
71f8d3d
Nov 12, 2018
Unitech
force-pushed the
Unitech:development
branch
2 times, most recently
from
7641d49
to
495c77f
Dec 18, 2018
ccanete
added some commits
Jan 17, 2019
Unitech
force-pushed the
Unitech:development
branch
3 times, most recently
from
ca13ded
to
741144e
Mar 7, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
ccanete commentedOct 27, 2018
•
edited
If using restart_delay, min_uptime and max_restarts all together, unstable_restarts might not be correctly incremented if a restart_delay exists