[
https://issues.apache.org/jira/browse/KAFKA-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16952410#comment-16952410
]
ASF GitHub Bot commented on KAFKA-8047:
---------------------------------------
alex-dukhno commented on pull request #7526: KAFKA-8047 remove KafkaMbean when
network close
URL: https://github.com/apache/kafka/pull/7526
This PR adds logic to remove sensors for a particular node connection when
node disconnects.
In order to be more familiar with `JMXReporter`, `Metrics` and `Sensor`s
functionality I did some tests refactoring to make them more communicative (at
least from my point of view)
When a connection is established a KafkaMBean is registered, and each metric
is added as MBean attribute. MBean is removed only when all metrics are.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
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:
[email protected]
> remove KafkaMbean when network close
> ------------------------------------
>
> Key: KAFKA-8047
> URL: https://issues.apache.org/jira/browse/KAFKA-8047
> Project: Kafka
> Issue Type: Bug
> Components: clients, core
> Affects Versions: 0.10.2.0, 0.10.2.1, 0.10.2.2
> Reporter: limeng
> Priority: Critical
> Fix For: 2.2.3
>
>
> the broker server will be oom when
> * a large number of clients frequently close and reconnect
> * the clientId changes every time when reconnect，that gives rise to too much
> kafkaMbean in broker
> the reason is that broker forget to remove kafkaMbean when detect connection
> closes.
> h2.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
