Search + K

Command Palette

Search for a command to run...

Sign In

Stop rollup jobs

Deprecated
POST /_rollup/job/{id}/_stop
Copy endpoint

If you try to stop a job that does not exist, an exception occurs. If you try to stop a job that is already stopped, nothing happens.

Since only a stopped job can be deleted, it can be useful to block the API until the indexer has fully stopped. This is accomplished with the wait_for_completion query parameter, and optionally a timeout. For example:

POST _rollup/job/sensor/_stop?wait_for_completion=true&timeout=10s

The parameter blocks the API call from returning until either the job has moved to STOPPED or the specified time has elapsed. If the specified time elapses without the job moving to STOPPED, a timeout exception occurs.

Required authorization

  • Cluster privileges: manage_rollup

Parameters

path Path Parameters

Name Type
id required

Identifier for the rollup job.

type TypesId = string

query Query Parameters

Name Type
timeout

If wait_for_completion is true, the API blocks for (at maximum) the specified duration while waiting for the job to stop. If more than timeout time has passed, the API throws a timeout exception. NOTE: Even if a timeout occurs, the stop request is still processing and eventually moves the job to STOPPED. The timeout simply means the API call itself timed out while waiting for the status change.

type TypesDuration = string | "-1" | "0"
wait_for_completion

If set to true, causes the API to block until the indexer state completely stops. If set to false, the API returns immediately and the indexer is stopped asynchronously in the background.

boolean

Responses

200 application/json
{ stopped: boolean; }