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

Explain restart decision and display in alloc-status #984

Merged
merged 1 commit into from
Mar 25, 2016

Conversation

dadgar
Copy link
Contributor

@dadgar dadgar commented Mar 24, 2016

This PR adds an explanation to restart decisions and displays them in alloc-status

@@ -76,6 +93,7 @@ func (r *RestartTracker) GetState() (string, time.Duration) {

// Hot path if no attempts are expected
if r.policy.Attempts == 0 {
r.reason = ReasonNoRestartsAllowed
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't you need to acquire a lock before setting the reason.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is locked at the top of GetState

@dadgar dadgar force-pushed the f-unrecoverable-error branch 2 times, most recently from 3ede6c9 to 2a4391d Compare March 25, 2016 19:30
@dadgar dadgar force-pushed the f-unrecoverable-error branch from 2a4391d to 6e779b8 Compare March 25, 2016 19:47
@dadgar dadgar merged commit 89c9fd1 into master Mar 25, 2016
@dadgar dadgar deleted the f-unrecoverable-error branch March 25, 2016 19:47
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants