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

System jobs should be running until stopped #2750

Merged
merged 2 commits into from
Jul 3, 2017
Merged

Conversation

schmichael
Copy link
Member

Prior to this commit they would be marked as dead if they had no
currently running allocations -- even though they would spring back to
life (running) if the cluster state changed such that a new eval+alloc
was created.

Prior to this commit they would be marked as dead if they had no
currently running allocations -- even though they would spring back to
life (running) if the cluster state changed such that a new eval+alloc
was created.
@schmichael schmichael requested a review from dadgar June 28, 2017 18:40
return structs.JobStatusDead, nil
}

if hasEval {
Copy link
Contributor

Choose a reason for hiding this comment

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

Lets just remove this and return running after checking if it has been explicitly stopped. The reason is that there could be no allocations (because no eligible nodes) and no evals because they have all garbage collected.

Copy link
Member Author

Choose a reason for hiding this comment

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

Ah! Right! I forgot about the gc'd evals case. Updating.

@schmichael schmichael force-pushed the b-system-jobs-running branch from c647983 to cd9da16 Compare July 3, 2017 20:48
@schmichael schmichael merged commit d16eb87 into master Jul 3, 2017
@schmichael schmichael deleted the b-system-jobs-running branch July 3, 2017 21:47
schmichael added a commit that referenced this pull request Jul 3, 2017
@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 Mar 31, 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