-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[ML] clear job size estimate cache when feature is reset #74494
Merged
benwtrent
merged 7 commits into
elastic:master
from
benwtrent:feature/ml-clear-model-size-cache-on-feature-reset
Jun 24, 2021
+110
−20
Merged
Changes from 4 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
97bfae9
[ML] clear job size estimate cache when feature is reset
benwtrent 3061baa
addressing PR comments and upping logging on failed test
benwtrent 0cfe27e
---remove this commit---
benwtrent b9f262f
fixing test and autoscaling logic
benwtrent 277e404
Update x-pack/plugin/ml/src/main/java/org/elasticsearch/xpack/ml/auto…
benwtrent ea208e6
Update MlAutoscalingDeciderService.java
benwtrent 50b4a11
Merge branch 'master' into feature/ml-clear-model-size-cache-on-featu…
elasticmachine File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
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.
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.
@droberts195 the test failure was a VALID test failure :). The test was taking advantage of the fact that the ml tracker was "up-to-date" due to the previous test.
When running the test directly, this is fine as the master node boots immediately and thus the memory is fresh.
When running the test AFTER another test, the cluster stays up and the tracker is reset.
So, to improve this behavior, I added this clause. It is a no-brainer really. Autoscaling should not check anything if there are
0
ML tasks and should be unaffected by memory tracker staleness.