elastic/elasticsearch

ETA for Reindex API

Open

#76,904 建立於 2021年8月25日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)Java (76,700 star) (25,882 fork)batch import
:Distributed/Reindex>enhancementTeam:Distributedhelp wanted

描述

The get task API (e.g. GET _tasks/lOHn4ATPST6LfKCW6m539w:517820) should include an estimated time of completion where applicable.

Specifically when using the reindex API, I had to write myself a basic tool some time ago to estimate when the task would be completed using the total, created, updated, start_time_in_millis, and running_time_in_nanos properties. (Although I believe in cases where the reindex operation omits some documents, this may not even be sufficient!)

It would be great if this functionality was built into this API.

貢獻者指南

技術棧
javarest api
領域
apisearchobservability
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Elasticsearch task frameworkREST API endpointsJava concurrencyTime estimation logic
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
20
研究方向
Investigate the Elasticsearch task management system, specifically the get task API implementation at `GET tasks/{taskId}`. Understand how the reindex operation tracks progress using fields like `total`, `created`, `updated`, `start time in millis`, and `running time in nanos`. Research potential algorithms like exponential moving average to estimate ETA, considering that documents may be omitted. Review existing discussions in the issue and any linked resources. Look at the `TasksClient.java` and `TransportTasksAction.java` source files for implementation details. Proposing adding an `estimated completion time` field to the task response is a starting point.