[ML] fixing testTwoJobsWithSameRandomizeSeedUseSameTrainingSet tests#62976
Merged
benwtrent merged 1 commit intoelastic:masterfrom Sep 29, 2020
Merged
Conversation
Collaborator
|
Pinging @elastic/ml-core (:ml) |
droberts195
approved these changes
Sep 29, 2020
droberts195
left a comment
There was a problem hiding this comment.
This is OK as a fix for the test, but I don't like that we're having to change tests that are doing things that users could be doing (running two jobs together on a clean system).
It all goes back to the problem that searches treat indices that don't exist differently to indices that have just been created and are not yet ready to use (but which are obviously empty as they've only just been created). I will bump the thread about doing something about that.
Member
Author
100% agree. I wish this "fix" was not necessary. |
benwtrent
added a commit
to benwtrent/elasticsearch
that referenced
this pull request
Sep 29, 2020
…lastic#62976) This fixes the two test failures. The shard failure seems to be due to the .ml-stats index being in the middle of being created.
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
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.
This fixes the two test failures.
The shard failure seems to be due to the .ml-stats index being in the middle of being created.
See:
elasticsearch/x-pack/plugin/ml/src/main/java/org/elasticsearch/xpack/ml/action/TransportStartDataFrameAnalyticsAction.java
Lines 391 to 405 in d1e963e
We fail grabbing the progress on starting the second job.
This commit splits the creating/starting of the two jobs.
We still want to fail on shard failures like this as knowing the previous progress (if it exists) is vitally important.
closes #62064
closes #55807