elasticsearch runtime_error ai_generated true

ElasticsearchTimeoutException: 任务 [id:12345] 因超时在 [30000ms] 后被取消，等待完成时触发

ElasticsearchTimeoutException: task [id:12345] cancelled with reason [timeout] after [30000ms] while waiting for completion

ID: elasticsearch/task-cancellation-timeout

其他格式: JSON · Markdown 中文 · English
79%修复率
83%置信度
1证据数
2024-01-20首次发现

版本兼容性

版本状态引入弃用备注
7.15.0 active — — —
7.17.15 active — — —
8.6.0 active — — —
8.10.0 active — — —

根因分析

长时间运行的任务（如重新索引、强制合并、快照）超过了配置的超时或取消阈值，导致提前终止。

English

A long-running task (e.g., reindex, force merge, snapshot) exceeded the configured timeout or cancellation threshold, leading to premature termination.

generic

官方文档

https://www.elastic.co/guide/en/elasticsearch/reference/current/tasks.html#task-cancellation

解决方案

  1. Increase the task timeout for the specific operation: POST _reindex?wait_for_completion=false&timeout=10m { "source": { "index": "old" }, "dest": { "index": "new" } }
  2. Check and update cluster-level task cancellation settings: PUT _cluster/settings { "persistent": { "task.max_cancellation_timeout": "120s" } }
  3. Retry the task with a smaller batch size or fewer shards to reduce execution time: POST _reindex { "source": { "index": "old", "size": 500 }, "dest": { "index": "new" } }

无效尝试

常见但无效的做法:

  1. 60% 失败

    The error may be due to cluster-wide task cancellation settings (e.g., `task.max_cancellation_timeout`), not just the request timeout. Overriding locally may be ignored.

  2. 85% 失败

    Task cancellation is recorded in cluster state, and restarting a single node does not reset the task manager on other nodes. The task will still be cancelled.

  3. 40% 失败

    This is a security risk and may cause resource leaks. Also, it requires a node restart, which may not be feasible in production.