elastic/elasticsearch

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

Open

#25,896 建立於 2017年7月26日

在 GitHub 查看
 (6 留言) (0 反應) (1 負責人)Java (76,700 star) (25,882 fork)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
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
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.