Skip to content
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] Jobs do not recover if the cluster state is deleted #30088

Closed
elasticmachine opened this issue Sep 12, 2017 · 2 comments
Closed

[ML] Jobs do not recover if the cluster state is deleted #30088

elasticmachine opened this issue Sep 12, 2017 · 2 comments
Labels
>bug :ml Machine learning

Comments

@elasticmachine
Copy link
Collaborator

Original comment by @sophiec20:

There are "rare" occasions when the cluster state may be manually deleted. For example, if a new trial license is wanted, or if the cluster state is red and cannot be recovered. This is not a recommended way to recover, but might be the last ditch option to try in some circumstances.

If the cluster state is removed rm -rf _state then upon an elasticsearch restart, the indices are recreated based upon files seen on disk.

If this occurs, ML job and datafeed configurations are not recreated (amongst other things). However the results and state indices are. It would not be possible to view these ML jobs without some black magic in play, and knowledge of the exact ML configuration details.

There are no plans yet to address or mitigate this, nor any easy resolution. Noting for informational purposes.

@elasticmachine elasticmachine added :ml Machine learning >bug labels Apr 25, 2018
@dimitris-athanasiou
Copy link
Contributor

I think this will be solved when we move the jobs/datafeeds off the cluster state.

@davidkyle
Copy link
Member

ML jobs are now stored in the index. Closed by #32905

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :ml Machine learning
Projects
None yet
Development

No branches or pull requests

3 participants