[ML] improve the autoscaling decider reason messages #69227
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
Pinging @elastic/ml-core (Team:ML) |
...gin/ml/src/main/java/org/elasticsearch/xpack/ml/autoscaling/MlAutoscalingDeciderService.java
Show resolved
Hide resolved
...l/src/test/java/org/elasticsearch/xpack/ml/autoscaling/MlAutoscalingDeciderServiceTests.java
Show resolved
Hide resolved
Member
Author
|
@elasticmachine update branch |
Member
Author
|
run elasticsearch-ci/2 |
benwtrent
deleted the
feature/ml-improve-autoscaling-decider-reason-msgs
branch
benwtrent
added a commit
to benwtrent/elasticsearch
that referenced
this pull request
Feb 19, 2021
It can be difficult to fully grok why a scaling decision was made. This commit improves the messaging to with additional information on two different no_scale decisions.
benwtrent
added a commit
that referenced
this pull request
Feb 22, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It can be difficult to fully grok why a scaling decision was made.
This commit improves the messaging to with additional information on two different
no_scaledecisions.