elastic/elasticsearch

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

Open

#25896 opened on Jul 26, 2017

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

Description

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.

Contributor guide

Tech stack
java
Domain
performanceobservability
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Knowledge of Elasticsearch internalsJava programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
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.