elastic/elasticsearch

we should add monitor about whether the netty worker thread pool are busy or not

Open

#80,340 opened on Nov 4, 2021

View on GitHub
 (13 comments) (0 reactions) (0 assignees)Java (76,700 stars) (25,882 forks)batch import
:Distributed/Network>enhancementTeam:Distributedhelp wanted

Description

We find the took in response is smaller than the external statistics timeout in product, part of the reason is that some threads of worker thread pool are relatively busy, the search requests are pending on the worker queue. Yet there is not available api, to get the statistics of worker queue, we have to add metrics and build the source code, If fact, There is a serious queuing here: 97, 64, 68, 108, 133, 61, 62, 123, 70, 66, 118, 110, 65, 52, 95, each number represents one of the worker threads's pending tasks.

If we can add api to get those metrics.

Contributor guide

Tech stack
java
Domain
backendobservability
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
JavaElasticsearch architectureNetty thread pool
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the Netty thread pool usage in Elasticsearch, particularly in the transport netty4 module. Look at existing metrics endpoints like / nodes/stats to understand the pattern for exposing new metrics. Review the issue comments for any prior discussion or pointers.
we should add monitor about whether the netty worker thread pool are busy or not · elastic/elasticsearch#80340 | Good First Issue