-
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] Store ml job configurations in the new .ml-config index #36698
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
Index mappings for the configuration documents
This changes the delete filter action to search for jobs using the filter to be deleted in the index rather than the cluster state.
Enables the ml integration tests excluding the rolling upgrade tests and a lot of fixes to make the tests pass again.
Conflicts due to the deprecation of AbstractComponent and removal of settings
This is the 6.6/6.7 implementation of a master node service to keep track of the native process memory requirement of each ML job with an associated native process. The new ML memory tracker service works when the whole cluster is upgraded to at least version 6.6. For mixed version clusters the old mechanism of established model memory stored on the job in cluster state is used. This means that the old (and complex) code to keep established model memory up to date on the job object cannot yet be removed. When this change is forward ported to 7.0 the old way of keeping established model memory updated will be removed.
This enables calls to the job and datafeed APIs in a mixed cluster state before jobs have been migrated
Because the cluster was expanded from 1 node to 3 indices would initially start off with 0 replicas. If the original node was killed before auto-expansion to 1 replica was complete then the test would fail because the indices would be unavailable.
Job updates can apply to cluster state or index jobs this includes reverting a model snapshot and finalizing the job
#35598) Small fixes to read from all locations and added index mappings for DelayedDataCheckConfig
After #36069 the approach for reallocating ML persistent tasks after refreshing job memory requirements can be simplified.
Two problems: 1. Stack overflow during async iteration when lots of jobs on same machine 2. Not effectively setting search size in all cases
The same cases are covered in MlMigrationIT
We don't need a Future to wait for completion
Pinging @elastic/ml-core |
retest this please |
run gradle build tests 2 |
droberts195
approved these changes
Dec 18, 2018
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 on the basis these changes have been previously reviewed in the feature branch PRs
hendrikmuhs
pushed a commit
that referenced
this pull request
Dec 31, 2018
hendrikmuhs
pushed a commit
that referenced
this pull request
Dec 31, 2018
hendrikmuhs
pushed a commit
that referenced
this pull request
Dec 31, 2018
davidkyle
changed the title
[ML] Merge the Jindex 6x feature branch
[ML] Store ml job configurations in the new .ml-config index
Jan 18, 2019
48 tasks
24 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.
Store ml anomaly detector jobs and datafeed configurations in the .ml-config index.
Prior to this change job configs were stored in the clusterstate, with this change all new jobs will stored in the new .ml-config index. Version 7 will expect all ml configurations to be stored in the index rather than clusterstate as a step towards that goal all closed job configs will be migrated from the clusterstate to the config index after upgrading.
This commit merges work undertaken on a feature branch.
See #32905