Pankaj260100 commented on code in PR #17100: URL: https://github.com/apache/druid/pull/17100#discussion_r1765381120
########## 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: @abhishekagarwal87, we are not setting the thread pool executor in the HttpClientModule. In the jetty server module, we also expose queue size from the thread pool; so is there any other way we can emit queue size here in HttpClientModule? -- 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]
