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

Reset Queued allocs to zero when job stopped #4414

Merged
merged 1 commit into from
Jul 16, 2018
Merged

Reset Queued allocs to zero when job stopped #4414

merged 1 commit into from
Jul 16, 2018

Conversation

dadgar
Copy link
Contributor

@dadgar dadgar commented Jun 13, 2018

When a job is stopped but not purged, we should set the Queued count to
be zero.

When a job is stopped but not purged, we should set the Queued count to
be zero.
@dadgar dadgar merged commit bc559d4 into master Jul 16, 2018
@dadgar dadgar deleted the b-stop-summary branch July 16, 2018 21:32
@tantra35
Copy link
Contributor

@dadgar Can this be as fix for problem when some jobs(3-4) with big allocations count(500 - 1200) stoped with nomad stop, and this operation can stuck nomad(nomad servers began eat too many memory, raft.db grows, and become unresponsive, but in usual case nomad operate normally), and we have problem described in #4477

@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 Feb 28, 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.

None yet

4 participants