mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-24 23:27:25 -04:00
[ML] Fix race condition when force stopping DF analytics job (#57680)
When we force delete a DF analytics job, we currently first force stop it and then we proceed with deleting the job config. This may result in logging errors if the job config is deleted before it is retrieved while the job is starting. Instead of force stopping the job, it would make more sense to try to stop the job gracefully first. So we now try that out first. If normal stop fails, then we resort to force stopping the job to ensure we can go through with the delete. In addition, this commit introduces `timeout` for the delete action and makes use of it in the child requests.
This commit is contained in:
parent
1d1beac7e0
commit
e116ac850f
11 changed files with 114 additions and 22 deletions
|
@ -27,10 +27,11 @@ The following arguments are optional:
|
|||
|
||||
["source","java",subs="attributes,callouts,macros"]
|
||||
---------------------------------------------------
|
||||
include-tagged::{doc-tests-file}[{api}-request-force]
|
||||
include-tagged::{doc-tests-file}[{api}-request-options]
|
||||
---------------------------------------------------
|
||||
<1> Use to forcefully delete a job that is not stopped. This method is quicker than stopping
|
||||
and deleting the job. Defaults to `false`.
|
||||
<2> Use to set the time to wait until the job is deleted. Defaults to 1 minute.
|
||||
|
||||
include::../execution.asciidoc[]
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue