[jira] [Updated] (KAFKA-8047) remove KafkaMbean when network close
[ https://issues.apache.org/jira/browse/KAFKA-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-8047: - Fix Version/s: (was: 2.2.2) 2.2.3 > 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.2#803003)
[jira] [Updated] (KAFKA-8047) remove KafkaMbean when network close
[ https://issues.apache.org/jira/browse/KAFKA-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-8047: --- Fix Version/s: (was: 2.2.1) 2.2.2 > 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.2 > > > 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 (v7.6.3#76005)
