f49a14ce6f
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. Backport of #57680 |
||
|---|---|---|
| .. | ||
| anomaly-detection | ||
| df-analytics/apis | ||
| images | ||
| ml-shared.asciidoc | ||