Skip to content

Conversation

@jan-elastic
Copy link
Contributor

No description provided.

@elasticsearchmachine elasticsearchmachine added needs:triage Requires assignment of a team area label v9.0.0 labels Oct 29, 2024
@jan-elastic jan-elastic added >non-issue :ml Machine learning Team:ML Meta label for the ML team v8.16.0 v8.17.0 and removed needs:triage Requires assignment of a team area label labels Oct 29, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/ml-core (Team:ML)

return assignmentState;
}
if (taskParams.getNumberOfAllocations() == 0) {
return AssignmentState.STARTED;
Copy link
Contributor Author

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.

@jan-elastic jan-elastic added the auto-backport Automatically create backport pull requests when merged label Oct 29, 2024
@jan-elastic jan-elastic merged commit d18824d into main Oct 29, 2024
17 checks passed
@jan-elastic jan-elastic deleted the assignment-state-started-zero-allocs branch October 29, 2024 12:47
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

The backport operation could not be completed due to the following error:

An unexpected error occurred when attempting to backport this PR.

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 115824

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-backport Automatically create backport pull requests when merged backport pending :ml Machine learning >non-issue Team:ML Meta label for the ML team v8.16.0 v8.17.0 v9.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants