Tasks
- class elasticsearch.client.TasksClient(client)
- Parameters:
client (BaseClient)
- cancel(*, task_id=None, actions=None, error_trace=None, filter_path=None, human=None, nodes=None, parent_task_id=None, pretty=None, wait_for_completion=None)
Cancel a task. WARNING: The task management API is new and should still be considered a beta feature. The API may change in ways that are not backwards compatible. A task may continue to run for some time after it has been cancelled because it may not be able to safely stop its current activity straight away. It is also possible that Elasticsearch must complete its work on other tasks before it can process the cancellation. The get task information API will continue to list these cancelled tasks until they complete. The cancelled flag in the response indicates that the cancellation command has been processed and the task will stop as soon as possible. To troubleshoot why a cancelled task does not complete promptly, use the get task information API with the ?detailed parameter to identify the other tasks the system is running. You can also use the node hot threads API to obtain detailed information about the work the system is doing instead of completing the cancelled task.
https://www.elastic.co/guide/en/elasticsearch/reference/8.17/tasks.html
- Parameters:
actions (str | Sequence[str] | None) – A comma-separated list or wildcard expression of actions that is used to limit the request.
nodes (Sequence[str] | None) – A comma-separated list of node IDs or names that is used to limit the request.
parent_task_id (str | None) – A parent task ID that is used to limit the tasks.
wait_for_completion (bool | None) – If true, the request blocks until all found tasks are complete.
error_trace (bool | None)
human (bool | None)
pretty (bool | None)
- Return type:
- get(*, task_id, error_trace=None, filter_path=None, human=None, pretty=None, timeout=None, wait_for_completion=None)
Get task information. Get information about a task currently running in the cluster. WARNING: The task management API is new and should still be considered a beta feature. The API may change in ways that are not backwards compatible. If the task identifier is not found, a 404 response code indicates that there are no resources that match the request.
https://www.elastic.co/guide/en/elasticsearch/reference/8.17/tasks.html
- Parameters:
task_id (str) – The task identifier.
timeout (str | Literal[-1] | ~typing.Literal[0] | None) – The period to wait for a response. If no response is received before the timeout expires, the request fails and returns an error.
wait_for_completion (bool | None) – If true, the request blocks until the task has completed.
error_trace (bool | None)
human (bool | None)
pretty (bool | None)
- Return type:
- list(*, actions=None, detailed=None, error_trace=None, filter_path=None, group_by=None, human=None, master_timeout=None, nodes=None, parent_task_id=None, pretty=None, timeout=None, wait_for_completion=None)
Get all tasks. Get information about the tasks currently running on one or more nodes in the cluster. WARNING: The task management API is new and should still be considered a beta feature. The API may change in ways that are not backwards compatible. Identifying running tasks The X-Opaque-Id header, when provided on the HTTP request header, is going to be returned as a header in the response as well as in the headers field for in the task information. This enables you to track certain calls or associate certain tasks with the client that started them. For example:
` curl -i -H "X-Opaque-Id: 123456" "http://localhost:9200/_tasks?group_by=parents" `
The API returns the following result:` HTTP/1.1 200 OK X-Opaque-Id: 123456 content-type: application/json; charset=UTF-8 content-length: 831 { "tasks" : { "u5lcZHqcQhu-rUoFaqDphA:45" : { "node" : "u5lcZHqcQhu-rUoFaqDphA", "id" : 45, "type" : "transport", "action" : "cluster:monitor/tasks/lists", "start_time_in_millis" : 1513823752749, "running_time_in_nanos" : 293139, "cancellable" : false, "headers" : { "X-Opaque-Id" : "123456" }, "children" : [ { "node" : "u5lcZHqcQhu-rUoFaqDphA", "id" : 46, "type" : "direct", "action" : "cluster:monitor/tasks/lists[n]", "start_time_in_millis" : 1513823752750, "running_time_in_nanos" : 92133, "cancellable" : false, "parent_task_id" : "u5lcZHqcQhu-rUoFaqDphA:45", "headers" : { "X-Opaque-Id" : "123456" } } ] } } } `
In this example, X-Opaque-Id: 123456 is the ID as a part of the response header. The X-Opaque-Id in the task headers is the ID for the task that was initiated by the REST request. The X-Opaque-Id in the children headers is the child task of the task that was initiated by the REST request.https://www.elastic.co/guide/en/elasticsearch/reference/8.17/tasks.html
- Parameters:
actions (str | Sequence[str] | None) – A comma-separated list or wildcard expression of actions used to limit the request. For example, you can use cluser:* to retrieve all cluster-related tasks.
detailed (bool | None) – If true, the response includes detailed information about the running tasks. This information is useful to distinguish tasks from each other but is more costly to run.
group_by (str | Literal['nodes', 'none', 'parents'] | None) – A key that is used to group tasks in the response. The task lists can be grouped either by nodes or by parent tasks.
master_timeout (str | Literal[-1] | ~typing.Literal[0] | None) – The period to wait for a connection to the master node. If no response is received before the timeout expires, the request fails and returns an error.
nodes (str | Sequence[str] | None) – A comma-separated list of node IDs or names that is used to limit the returned information.
parent_task_id (str | None) – A parent task identifier that is used to limit returned information. To return all tasks, omit this parameter or use a value of -1. If the parent task is not found, the API does not return a 404 response code.
timeout (str | Literal[-1] | ~typing.Literal[0] | None) – The period to wait for each node to respond. If a node does not respond before its timeout expires, the response does not include its information. However, timed out nodes are included in the node_failures property.
wait_for_completion (bool | None) – If true, the request blocks until the operation is complete.
error_trace (bool | None)
human (bool | None)
pretty (bool | None)
- Return type: