-
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] Writing Results Retries Continue After Analytics Job Stopped #53687
Comments
Pinging @elastic/ml-core (:ml) |
blaklaybul
changed the title
[ML] Writing Results Retries Continues After Analytics Stopped
[ML] Writing Results Retries Continue After Analytics Job Stopped
Mar 17, 2020
I think this shows two problems:
|
benwtrent
added a commit
that referenced
this issue
Mar 19, 2020
… and stop retrying when analytics job is stopping (#53725) This fixes two issues: - Results persister would retry actions even if they are not intermittent. An example of an persistent failure is a doc mapping problem. - Data frame analytics would continue to retry to persist results even after the job is stopped. closes #53687
benwtrent
added a commit
to benwtrent/elasticsearch
that referenced
this issue
Mar 19, 2020
… and stop retrying when analytics job is stopping (elastic#53725) This fixes two issues: - Results persister would retry actions even if they are not intermittent. An example of an persistent failure is a doc mapping problem. - Data frame analytics would continue to retry to persist results even after the job is stopped. closes elastic#53687
benwtrent
added a commit
that referenced
this issue
Mar 19, 2020
…ittent and stop retrying when analytics job is stopping (#53725) (#53808) * [ML] only retry persistence failures when the failure is intermittent and stop retrying when analytics job is stopping (#53725) This fixes two issues: - Results persister would retry actions even if they are not intermittent. An example of an persistent failure is a doc mapping problem. - Data frame analytics would continue to retry to persist results even after the job is stopped. closes #53687
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This was found on a recent 7.7 build. I created a classification analysis that became stuck in the
writing_results
phase.Stopping the job via the UI removed the job from the jobs list, but the job remains in a
stopping
state. The retires continue even after stopping the job:job config:
The text was updated successfully, but these errors were encountered: