elastic/elasticsearch

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

Open

#80,340 建立於 2021年11月4日

在 GitHub 查看
 (13 留言) (0 反應) (0 負責人)Java (76,700 star) (25,882 fork)batch import
:Distributed/Network>enhancementTeam:Distributedhelp wanted

描述

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.

貢獻者指南

技術棧
java
領域
backendobservability
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaElasticsearch architectureNetty thread pool
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
25
研究方向
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.