[ML] Prefer cluster state config to index documents #36014
Merged
Conversation
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 reverts commit 417624f.
|
Pinging @elastic/ml-core |
|
No issues with the PR really, but what is the reasoning for the reverting? Why should we prefer the cluster state over the indexed configs? |
benwtrent
approved these changes
Nov 28, 2018
There was a problem hiding this comment.
Well @davidkyle , there you stand, with your code in your hands:
https://www.youtube.com/watch?v=c0SvsinEUfY
:D
|
Actually doing this uncovered a bug where on closing a job the check that the job's datafeed must be stopped was only checking the index configs and not the clusterstate jobs. This explains an intermittent failure I'd seen in the rolling upgrade tests. |
43 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A partial revert of #35940
Duplicate configs in both the clusterstate and index are still possible but now clusterstate config is preferred.
After discussing the changes in #35940 it was decided that during a move operation the original should always be preferred to the new until the operation has completed. This revert also makes the code simpler to read.
Alas the wasted time
@benwtrent you reviewed #35940 would you take a look at this please