-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Blocked evaluation fixes #4867
Blocked evaluation fixes #4867
Conversation
The old logic for cancelling duplicate blocked evaluations by job id had the issue where the newer evaluation could have additional node classes that it is (in)eligible for that we would not capture. This could make it such that cluster state could change such that the job would make progress but no evaluation was unblocked.
Blocked evaluation fixes
t.Fatalf("bad: %#v", bStats) | ||
} | ||
|
||
// Add an older evaluation and assert it gets cancelled |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you also add a test case for the other way around (add an eval thats older than the current one so that its marked as the duplicate)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
e1-e3 are that, e4 tests that we can cancel the incoming
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. |
This PR has two blocked evaluation fixes:
Job tracking in the blocked eval tracker now handles namespaces
Improve cancelling of duplicate blocked evaluations such that new
information is not lost