elastic/elasticsearch

ETA for Reindex API

Open

#76,904 opened on 2021年8月25日

GitHub で見る
 (2 comments) (0 reactions) (0 assignees)Java (76,700 stars) (25,882 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
4
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.