2017-04-11 21:52:47 -04:00
|
|
|
//lcawley Verified example output 2017-04-11
|
2017-04-04 18:26:39 -04:00
|
|
|
[[ml-close-job]]
|
|
|
|
==== Close Jobs
|
|
|
|
|
2017-04-11 21:52:47 -04:00
|
|
|
The close job API enables you to close a job.
|
|
|
|
A job can be opened and closed multiple times throughout its lifecycle.
|
2017-04-04 18:26:39 -04:00
|
|
|
|
2017-04-19 13:52:30 -04:00
|
|
|
A closed job cannot receive data or perform analysis
|
|
|
|
operations, but you can still explore and navigate results.
|
|
|
|
|
2017-04-25 17:08:29 -04:00
|
|
|
|
2017-04-04 18:26:39 -04:00
|
|
|
===== Request
|
|
|
|
|
|
|
|
`POST _xpack/ml/anomaly_detectors/<job_id>/_close`
|
|
|
|
|
2017-04-25 17:08:29 -04:00
|
|
|
|
2017-04-04 18:26:39 -04:00
|
|
|
===== Description
|
|
|
|
|
2017-04-11 21:52:47 -04:00
|
|
|
//A job can be closed once all data has been analyzed.
|
2017-04-04 18:26:39 -04:00
|
|
|
|
|
|
|
When you close a job, it runs housekeeping tasks such as pruning the model history,
|
2017-04-11 21:52:47 -04:00
|
|
|
flushing buffers, calculating final results and persisting the model snapshots.
|
2017-04-04 18:26:39 -04:00
|
|
|
Depending upon the size of the job, it could take several minutes to close and
|
|
|
|
the equivalent time to re-open.
|
|
|
|
|
2017-04-19 13:52:30 -04:00
|
|
|
After it is closed, the job has a minimal overhead on the cluster except for
|
2017-04-24 14:14:58 -04:00
|
|
|
maintaining its meta data. Therefore it is a best practice to close jobs that
|
|
|
|
are no longer required to process data.
|
2017-04-19 13:52:30 -04:00
|
|
|
|
2017-05-02 15:45:42 -04:00
|
|
|
When a {dfeed} that has a specified end date stops, it automatically closes
|
2017-04-24 14:14:58 -04:00
|
|
|
the job.
|
|
|
|
|
|
|
|
NOTE: If you use the `force` query parameter, the request returns before the
|
|
|
|
associated actions such as flushing buffers and persisting the model snapshots
|
|
|
|
complete. Therefore, do not use that parameter in a script that expects the job
|
|
|
|
to be in a consistent state after the close job API returns.
|
2017-04-04 18:26:39 -04:00
|
|
|
|
|
|
|
|
|
|
|
===== Path Parameters
|
|
|
|
|
|
|
|
`job_id` (required)::
|
2017-04-11 22:26:18 -04:00
|
|
|
(string) Identifier for the job
|
2017-04-04 18:26:39 -04:00
|
|
|
|
2017-04-25 17:08:29 -04:00
|
|
|
|
2017-04-04 18:26:39 -04:00
|
|
|
===== Query Parameters
|
|
|
|
|
2017-04-19 13:52:30 -04:00
|
|
|
`force`::
|
2017-04-24 14:14:58 -04:00
|
|
|
(boolean) Use to close a failed job, or to forcefully close a job which has not
|
2017-04-19 13:52:30 -04:00
|
|
|
responded to its initial close request.
|
|
|
|
|
2017-04-24 14:14:58 -04:00
|
|
|
`timeout`::
|
|
|
|
(time units) Controls the time to wait until a job has closed.
|
|
|
|
The default value is 30 minutes.
|
|
|
|
|
2017-04-19 13:52:30 -04:00
|
|
|
|
2017-04-25 17:08:29 -04:00
|
|
|
===== Authorization
|
|
|
|
|
|
|
|
You must have `manage_ml`, or `manage` cluster privileges to use this API.
|
|
|
|
For more information, see <<privileges-list-cluster>>.
|
|
|
|
|
2017-04-04 18:26:39 -04:00
|
|
|
|
|
|
|
===== Examples
|
|
|
|
|
|
|
|
The following example closes the `event_rate` job:
|
|
|
|
|
|
|
|
[source,js]
|
|
|
|
--------------------------------------------------
|
|
|
|
POST _xpack/ml/anomaly_detectors/event_rate/_close
|
|
|
|
--------------------------------------------------
|
|
|
|
// CONSOLE
|
|
|
|
// TEST[skip:todo]
|
|
|
|
|
|
|
|
When the job is closed, you receive the following results:
|
2017-04-21 11:23:27 -04:00
|
|
|
[source,js]
|
2017-04-04 18:26:39 -04:00
|
|
|
----
|
|
|
|
{
|
|
|
|
"closed": true
|
|
|
|
}
|
|
|
|
----
|