All job configuration, model state and results are deleted. It is not currently possible to delete multiple jobs using wildcards or a comma separated list. If you delete a job that has a datafeed, the request first tries to delete the datafeed. This behavior is equivalent to calling the delete datafeed API with the same timeout and force parameters as the delete job request. ##Required authorization
- Cluster privileges:
manage_ml
Query parameters
-
Use to forcefully delete an opened job; this method is quicker than closing and deleting the job.
-
Specifies whether annotations that have been added by the user should be deleted along with any auto-generated annotations when the job is reset.
-
Specifies whether the request should return immediately or wait until the job deletion completes.
DELETE
/_ml/anomaly_detectors/{job_id}
Console
DELETE _ml/anomaly_detectors/total-requests
curl \
--request DELETE 'http://api.example.com/_ml/anomaly_detectors/{job_id}'
Response examples (200)
Delete job
A successful response when deleting an anomaly detection job.
{
"acknowledged": true
}
A successful response when deleting an anomaly detection job asynchronously. When the `wait_for_completion` query parameter is set to `false`, the response contains an identifier for the job deletion task.
{
"task": "oTUltX4IQMOUUVeiohTt8A:39"
}