-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Fix deployment_stats.state for target_allocation_count=0 #114570
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) |
|
|
||
| public State calculateState() { | ||
| if (allocationCount == 0) { | ||
| if (allocationCount == 0 && targetAllocationCount > 0) { |
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.
In case of targetAllocationCount == 0, this logic was returning STARTING. Changed that to FULLY_ALLOCATED.
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.
Note: this incorrect allocation state also caused ML autoscaling to not scale down, see:
- https://github.com/elastic/elasticsearch/blob/main/x-pack/plugin/ml/src/main/java/org/elasticsearch/xpack/ml/autoscaling/MlMemoryAutoscalingDecider.java#L194
- https://github.com/elastic/elasticsearch/blob/main/x-pack/plugin/ml/src/main/java/org/elasticsearch/xpack/ml/autoscaling/MlAutoscalingContext.java#L183-L195
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.
LGTM
💔 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.