-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Set assignment state to "started" in case of zero allocations #115824
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
Conversation
|
Pinging @elastic/ml-core (Team:ML) |
| return assignmentState; | ||
| } | ||
| if (taskParams.getNumberOfAllocations() == 0) { | ||
| return AssignmentState.STARTED; |
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.
There are code paths where you can get into state of numberOfAllocations=0 and assignmentState=STARTING. I think that can happen when the scheduler moves jobs around, which triggers the state to be recalculated here.
This causes issues, because assignments in a STARTING state cannot be updated, and an assignment with numberOfAllocations=0 won't get out of that state.
💔 Backport failedThe backport operation could not be completed due to the following error: You can use sqren/backport to manually backport by running |
No description provided.