[
https://issues.apache.org/jira/browse/KAFKA-8360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199404#comment-17199404
]
ASF GitHub Bot commented on KAFKA-8360:
---------------------------------------
viktorsomogyi edited a comment on pull request #220:
URL: https://github.com/apache/kafka-site/pull/220#issuecomment-696132637
Otherwise it looks good, I can approve it once you create the PR in the
kafka repo (and perhaps get someone to merge it).
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Docs do not mention RequestQueueSize JMX metric
> -----------------------------------------------
>
> Key: KAFKA-8360
> URL: https://issues.apache.org/jira/browse/KAFKA-8360
> Project: Kafka
> Issue Type: Improvement
> Components: documentation, metrics, network
> Reporter: Charles Francis Larrieu Casias
> Assignee: Ankit Kumar
> Priority: Major
> Labels: documentation
>
> In the [monitoring
> documentation|[https://kafka.apache.org/documentation/#monitoring],] there is
> no mention of the `kafka.network:type=RequestChannel,name=RequestQueueSize`
> JMX metric. This is an important metric because it can indicate that there
> are too many requests in queue and suggest either increasing
> `queued.max.requests` (along with perhaps memory), or increasing
> `num.io.threads`.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
