Pankaj260100 commented on code in PR #17100: URL: https://github.com/apache/druid/pull/17100#discussion_r1764660145
########## docs/operations/metrics.md: ########## @@ -133,6 +133,7 @@ Most metric values reset each emission period, as specified in `druid.monitoring |`jetty/threadPool/min`|Number of minimum threads allocatable.|`druid.server.http.numThreads` plus a small fixed number of threads allocated for Jetty acceptors and selectors.| |`jetty/threadPool/max`|Number of maximum threads allocatable.|`druid.server.http.numThreads` plus a small fixed number of threads allocated for Jetty acceptors and selectors.| |`jetty/threadPool/queueSize`|Size of the worker queue.|Not much higher than `druid.server.http.queueSize`.| +|`jetty/httpClient/threadpool/queueSize`|Size of the worker queue at jetty http client.|Less than or equal to 1024(default value).| Review Comment: This is to monitor if we have a sufficient number of Connections per destination. Let's suppose the latency is high at the broker. It might be possible the request was waiting at the jetty client-side queue, causing the latency to go high. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
