elastic/elasticsearch

Feature Request: Profile API should show node details as well as shard details

Open

#25,896 opened on 2017年7月26日

GitHub で見る
 (6 comments) (0 reactions) (1 assignee)Java (76,700 stars) (25,882 forks)batch import
:Search Foundations/Search>enhancementTeam:Search Foundationsgood first issue

説明

Describe the feature:

Currently the Profile API breaks down the timing information by shard. It would be useful if it could also list which node the shard is on such that one might be able to infer whether performance is a node-level issue. This is particularly useful where a shard might have a big replica count and its difficult to tell which shard copy on which node was the one that was hit by this search.

コントリビューターガイド

技術スタック
java
領域
performanceobservability
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Knowledge of Elasticsearch internalsJava programming
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
60
調査方針
The issue has an assignee and 6 comments; review those comments for any consensus or guidance. The Profile API is implemented in Java; locate the relevant classes that handle the API response, such as 'ProfileResult' or similar. Add node information by accessing the node ID from the shard context. Ensure the changes are backward compatible.