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

Reuse blocked evaluations and handle unblock events that occurred during scheduling #1199

Merged
merged 6 commits into from
May 25, 2016

Conversation

dadgar
Copy link
Contributor

@dadgar dadgar commented May 23, 2016

This PR:

  • Reuses existing blocked evaluations
  • Checks if there were unblock events that would have been of use to the blocked evaluation while it was in the scheduler
  • Periodically unblocks failed evaluations that hit the max Plan attempts.

@armon for review. Should be reviewed after #1188 is merged and this rebased.

@dadgar dadgar force-pushed the f-lighter-blocked-evals branch from 84fb757 to c7b7a9b Compare May 25, 2016 01:26
@dadgar dadgar force-pushed the f-lighter-blocked-evals branch from c7b7a9b to 8456f77 Compare May 25, 2016 03:11
@@ -133,6 +146,14 @@ func (b *BlockedEvals) Block(eval *structs.Evaluation) {
return
}

// Check if the eval missed an unblock while it was in the scheduler at an
// older index.
Copy link
Member

Choose a reason for hiding this comment

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

I would add some more comment as to how/why this is possible. "The scheduler could have been invoked with a snapshot of state that was prior to additional capacity being added or allocations becoming terminal."

@armon
Copy link
Member

armon commented May 25, 2016

LGTM

@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 24, 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