This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.

› › ›

cat pending tasks API

edit

cat pending tasks API

edit

cat APIs are only intended for human consumption using the command line or Kibana console. They are not intended for use by applications. For application consumption, use the pending cluster tasks API.

Returns cluster-level changes that have not yet been executed.

Request

edit

GET /_cat/pending_tasks

Prerequisites

edit

If the Elasticsearch security features are enabled, you must have the monitor or manage cluster privilege to use this API.

Query parameters

edit

format: (Optional, string) Short version of the HTTP accept header. Valid values include JSON, YAML, etc.
h: (Optional, string) Comma-separated list of column names to display.
help: (Optional, Boolean) If true, the response includes help information. Defaults to false.
local: (Optional, Boolean) If true, the request retrieves information from the local node only. Defaults to false, which means information is retrieved from the master node.
master_timeout: (Optional, time units) Period to wait for the master node. If the master node is not available before the timeout expires, the request fails and returns an error. Defaults to 30s. Can also be set to -1 to indicate that the request should never timeout.
s: (Optional, string) Comma-separated list of column names or column aliases used to sort the response.
time: (Optional, time units) Unit used to display time values.
v: (Optional, Boolean) If true, the response includes column headings. Defaults to false.

Examples

edit

resp = client.cat.pending_tasks(
    v=True,
)
print(resp)

response = client.cat.pending_tasks(
  v: true
)
puts response

const response = await client.cat.pendingTasks({
  v: "true",
});
console.log(response);

GET /_cat/pending_tasks?v=true

The API returns the following response:

insertOrder timeInQueue priority source
       1685       855ms HIGH     update-mapping [foo][t]
       1686       843ms HIGH     update-mapping [foo][t]
       1693       753ms HIGH     refresh-mapping [foo][[t]]
       1688       816ms HIGH     update-mapping [foo][t]
       1689       802ms HIGH     update-mapping [foo][t]
       1690       787ms HIGH     update-mapping [foo][t]
       1691       773ms HIGH     update-mapping [foo][t]

« cat nodes API cat plugins API »