[jira] [Updated] (KAFKA-10797) Build / JDK 8 / org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.testValidSaslPlainOverSsl failed
[ https://issues.apache.org/jira/browse/KAFKA-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] limeng updated KAFKA-10797: --- Description: There is one testcase running failed on jdk 8 version when submmit the pr:[https://github.com/apache/kafka/pull/9675.] but seems that no related among them. And there is no problem when build on jdk 11&15version. [https://github.com/apache/kafka/pull/9675/checks?check_run_id=1485855276] !image-2020-12-02-23-01-00-412.png! was: There is one testcase running failed on jdk 8 version when submmit the pr:[https://github.com/apache/kafka/pull/9675.] but seems that no related among them. And there is no problem when build on jdk 11&15version. [https://github.com/apache/kafka/pull/9675/checks?check_run_id=1485855276] !截屏2020-12-02 下午10.35.10.png! > Build / JDK 8 / > org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.testValidSaslPlainOverSsl > failed > - > > Key: KAFKA-10797 > URL: https://issues.apache.org/jira/browse/KAFKA-10797 > Project: Kafka > Issue Type: Test > Components: build > Environment: jdk 8 >Reporter: limeng >Assignee: limeng >Priority: Minor > Attachments: image-2020-12-02-23-01-00-412.png, 截屏2020-12-02 > 下午10.35.10.png > > > There is one testcase running failed on jdk 8 version when submmit the > pr:[https://github.com/apache/kafka/pull/9675.] but seems that no related > among them. > And there is no problem when build on jdk 11&15version. > [https://github.com/apache/kafka/pull/9675/checks?check_run_id=1485855276] > > !image-2020-12-02-23-01-00-412.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10797) Build / JDK 8 / org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.testValidSaslPlainOverSsl failed
[ https://issues.apache.org/jira/browse/KAFKA-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] limeng updated KAFKA-10797: --- Attachment: image-2020-12-02-23-01-00-412.png > Build / JDK 8 / > org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.testValidSaslPlainOverSsl > failed > - > > Key: KAFKA-10797 > URL: https://issues.apache.org/jira/browse/KAFKA-10797 > Project: Kafka > Issue Type: Test > Components: build > Environment: jdk 8 >Reporter: limeng >Assignee: limeng >Priority: Minor > Attachments: image-2020-12-02-23-01-00-412.png, 截屏2020-12-02 > 下午10.35.10.png > > > There is one testcase running failed on jdk 8 version when submmit the > pr:[https://github.com/apache/kafka/pull/9675.] but seems that no related > among them. > And there is no problem when build on jdk 11&15version. > [https://github.com/apache/kafka/pull/9675/checks?check_run_id=1485855276] > > !截屏2020-12-02 下午10.35.10.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10797) Build / JDK 8 / org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.testValidSaslPlainOverSsl failed
[ https://issues.apache.org/jira/browse/KAFKA-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] limeng updated KAFKA-10797: --- Description: There is one testcase running failed on jdk 8 version when submmit the pr:[https://github.com/apache/kafka/pull/9675.] but seems that no related among them. And there is no problem when build on jdk 11&15version. [https://github.com/apache/kafka/pull/9675/checks?check_run_id=1485855276] !截屏2020-12-02 下午10.35.10.png! was: There is one testcase running failed on jdk 8 version when submmit the pr:[https://github.com/apache/kafka/pull/9675.] but seems that no related among them. And there is no problem when build on jdk 11&15version. https://github.com/apache/kafka/pull/9675/checks?check_run_id=1485855276 > Build / JDK 8 / > org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.testValidSaslPlainOverSsl > failed > - > > Key: KAFKA-10797 > URL: https://issues.apache.org/jira/browse/KAFKA-10797 > Project: Kafka > Issue Type: Test > Components: build > Environment: jdk 8 >Reporter: limeng >Assignee: limeng >Priority: Minor > Attachments: 截屏2020-12-02 下午10.35.10.png > > > There is one testcase running failed on jdk 8 version when submmit the > pr:[https://github.com/apache/kafka/pull/9675.] but seems that no related > among them. > And there is no problem when build on jdk 11&15version. > [https://github.com/apache/kafka/pull/9675/checks?check_run_id=1485855276] > > !截屏2020-12-02 下午10.35.10.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10797) Build / JDK 8 / org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.testValidSaslPlainOverSsl failed
[ https://issues.apache.org/jira/browse/KAFKA-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] limeng updated KAFKA-10797: --- Attachment: 截屏2020-12-02 下午10.35.10.png > Build / JDK 8 / > org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.testValidSaslPlainOverSsl > failed > - > > Key: KAFKA-10797 > URL: https://issues.apache.org/jira/browse/KAFKA-10797 > Project: Kafka > Issue Type: Test > Components: build > Environment: jdk 8 >Reporter: limeng >Assignee: limeng >Priority: Minor > Attachments: 截屏2020-12-02 下午10.35.10.png > > > There is one testcase running failed on jdk 8 version when submmit the > pr:[https://github.com/apache/kafka/pull/9675.] but seems that no related > among them. > And there is no problem when build on jdk 11&15version. > https://github.com/apache/kafka/pull/9675/checks?check_run_id=1485855276 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10797) Build / JDK 8 / org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.testValidSaslPlainOverSsl failed
[ https://issues.apache.org/jira/browse/KAFKA-10797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] limeng updated KAFKA-10797: --- Docs Text: (was: org.junit.ComparisonFailure: expected:<[tXCQA2rulHkZ5bAwvA6x4prne0sKqqtC5Y6DBnMSeKzOJkDtoSNrWzJhXVuTO7slBDg31s4HXelbGUWmOilVkSw1K7lto4RjLnKD-8]> but was:<[��??PLAIN]> at org.junit.Assert.assertEquals(Assert.java:117) at org.junit.Assert.assertEquals(Assert.java:146) at org.apache.kafka.common.network.NetworkTestUtils.checkClientConnection(NetworkTestUtils.java:80) at org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.checkClientConnection(SaslAuthenticatorTest.java:2105) at org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.checkAuthenticationAndReauthentication(SaslAuthenticatorTest.java:2160) at org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.testValidSaslPlainOverSsl(SaslAuthenticatorTest.java:188) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63) at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329) at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293) at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306) at org.junit.runners.ParentRunner.run(ParentRunner.java:413) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) at org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:33) at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:94) at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:119) at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:36) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:182) at
[jira] [Created] (KAFKA-10797) Build / JDK 8 / org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.testValidSaslPlainOverSsl failed
limeng created KAFKA-10797: -- Summary: Build / JDK 8 / org.apache.kafka.common.security.authenticator.SaslAuthenticatorTest.testValidSaslPlainOverSsl failed Key: KAFKA-10797 URL: https://issues.apache.org/jira/browse/KAFKA-10797 Project: Kafka Issue Type: Test Components: build Environment: jdk 8 Reporter: limeng Assignee: limeng There is one testcase running failed on jdk 8 version when submmit the pr:[https://github.com/apache/kafka/pull/9675.] but seems that no related among them. And there is no problem when build on jdk 11&15version. https://github.com/apache/kafka/pull/9675/checks?check_run_id=1485855276 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10794) Replica leader election is too slow in the case of too many partitions
[ https://issues.apache.org/jira/browse/KAFKA-10794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] limeng updated KAFKA-10794: --- Description: There is more than 6000 topics and 300 brokers in my kafka cluster, and we frequently run kafka-preferred-replica-election.sh to rebalance our cluster. But the reblance process spendes too more time and cpu resource like the picture blow. We find that the function:'controllerContext.allPartitions' is invoked too many times. !截屏2020-12-02 上午11.43.48.png! !image-2020-12-02-15-23-43-384.png! was: There is more than 6000 topics and 300 brokers in my kafka cluster, and we frequently run kafka-preferred-replica-election.sh to rebalance our cluster. But the reblance process spendes too more time and cpu resource like the picture blow. We find that the function:'controllerContext.allPartitions' is invoked too many times. !截屏2020-12-02 上午11.43.48.png! > Replica leader election is too slow in the case of too many partitions > -- > > Key: KAFKA-10794 > URL: https://issues.apache.org/jira/browse/KAFKA-10794 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 2.6.0, 2.5.1 >Reporter: limeng >Priority: Major > Attachments: clipboard_image_1606806581629.png, > image-2020-12-02-15-23-43-384.png, 截屏2020-12-01 下午2.36.19.png, 截屏2020-12-02 > 上午11.43.48.png > > > There is more than 6000 topics and 300 brokers in my kafka cluster, and we > frequently run kafka-preferred-replica-election.sh to rebalance our cluster. > But the reblance process spendes too more time and cpu resource like the > picture blow. > We find that the function:'controllerContext.allPartitions' is invoked too > many times. > !截屏2020-12-02 上午11.43.48.png! > !image-2020-12-02-15-23-43-384.png! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10794) Replica leader election is too slow in the case of too many partitions
[ https://issues.apache.org/jira/browse/KAFKA-10794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] limeng updated KAFKA-10794: --- Attachment: image-2020-12-02-15-23-43-384.png > Replica leader election is too slow in the case of too many partitions > -- > > Key: KAFKA-10794 > URL: https://issues.apache.org/jira/browse/KAFKA-10794 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 2.6.0, 2.5.1 >Reporter: limeng >Priority: Major > Attachments: clipboard_image_1606806581629.png, > image-2020-12-02-15-23-43-384.png, 截屏2020-12-01 下午2.36.19.png, 截屏2020-12-02 > 上午11.43.48.png > > > There is more than 6000 topics and 300 brokers in my kafka cluster, and we > frequently run kafka-preferred-replica-election.sh to rebalance our cluster. > But the reblance process spendes too more time and cpu resource like the > picture blow. > We find that the function:'controllerContext.allPartitions' is invoked too > many times. > !截屏2020-12-02 上午11.43.48.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10794) Replica leader election is too slow in the case of too many partitions
[ https://issues.apache.org/jira/browse/KAFKA-10794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] limeng updated KAFKA-10794: --- Attachment: 截屏2020-12-01 下午2.36.19.png > Replica leader election is too slow in the case of too many partitions > -- > > Key: KAFKA-10794 > URL: https://issues.apache.org/jira/browse/KAFKA-10794 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 2.6.0, 2.5.1 >Reporter: limeng >Priority: Major > Attachments: clipboard_image_1606806581629.png, 截屏2020-12-01 > 下午2.36.19.png, 截屏2020-12-02 上午11.43.48.png > > > There is more than 6000 topics and 300 brokers in my kafka cluster, and we > frequently run kafka-preferred-replica-election.sh to rebalance our cluster. > But the reblance process spendes too more time and cpu resource like the > picture blow. > We find that the function:'controllerContext.allPartitions' is invoked too > many times. > !截屏2020-12-02 上午11.43.48.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10794) Replica leader election is too slow in the case of too many partitions
[ https://issues.apache.org/jira/browse/KAFKA-10794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] limeng updated KAFKA-10794: --- Description: There is more than 6000 topics and 300 brokers in my kafka cluster, and we frequently run kafka-preferred-replica-election.sh to rebalance our cluster. But the reblance process spendes too more time and cpu resource like the picture blow. We find that the function:'controllerContext.allPartitions' is invoked too many times. !截屏2020-12-02 上午11.43.48.png! was: There is more than 6000 topics and 300 brokers in my kafka cluster, and we set the config:'auto.leader.rebalance.enable=true'. The reblance process spendes too more time and cpu resource. We find that the function:'controllerContext.allPartitions' is invoked too many times. !截屏2020-12-02 上午11.43.48.png! > Replica leader election is too slow in the case of too many partitions > -- > > Key: KAFKA-10794 > URL: https://issues.apache.org/jira/browse/KAFKA-10794 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 2.6.0, 2.5.1 >Reporter: limeng >Priority: Major > Attachments: clipboard_image_1606806581629.png, 截屏2020-12-02 > 上午11.43.48.png > > > There is more than 6000 topics and 300 brokers in my kafka cluster, and we > frequently run kafka-preferred-replica-election.sh to rebalance our cluster. > But the reblance process spendes too more time and cpu resource like the > picture blow. > We find that the function:'controllerContext.allPartitions' is invoked too > many times. > !截屏2020-12-02 上午11.43.48.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10794) Replica leader election is too slow in the case of too many partitions
[ https://issues.apache.org/jira/browse/KAFKA-10794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] limeng updated KAFKA-10794: --- Description: There is more than 6000 topics and 300 brokers in my kafka cluster, and we set the config:'auto.leader.rebalance.enable=true'. The reblance process spendes too more time and cpu resource. We find that the function:'controllerContext.allPartitions' is invoked too many times. !截屏2020-12-02 上午11.43.48.png! was: There is more than 6000 topics and 300 brokers in my kafka cluster, and we set the config:'auto.leader.rebalance.enable=true'. The reblance process spendes too more time and cpu resource. We find that the function:'controllerContext.allPartitions' is invoked too many times. !clipboard_image_1606806581629.png! > Replica leader election is too slow in the case of too many partitions > -- > > Key: KAFKA-10794 > URL: https://issues.apache.org/jira/browse/KAFKA-10794 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 2.6.0, 2.5.1 >Reporter: limeng >Priority: Major > Attachments: clipboard_image_1606806581629.png, 截屏2020-12-02 > 上午11.43.48.png > > > There is more than 6000 topics and 300 brokers in my kafka cluster, and we > set the config:'auto.leader.rebalance.enable=true'. > The reblance process spendes too more time and cpu resource. > We find that the function:'controllerContext.allPartitions' is invoked too > many times. > !截屏2020-12-02 上午11.43.48.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10794) Replica leader election is too slow in the case of too many partitions
[ https://issues.apache.org/jira/browse/KAFKA-10794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] limeng updated KAFKA-10794: --- Attachment: clipboard_image_1606806581629.png > Replica leader election is too slow in the case of too many partitions > -- > > Key: KAFKA-10794 > URL: https://issues.apache.org/jira/browse/KAFKA-10794 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 2.6.0, 2.5.1 >Reporter: limeng >Priority: Major > Attachments: clipboard_image_1606806581629.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (KAFKA-10794) Replica leader election is too slow in the case of too many partitions
[ https://issues.apache.org/jira/browse/KAFKA-10794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] limeng updated KAFKA-10794: --- Description: There is more than 6000 topics and 300 brokers in my kafka cluster, and we set the config:'auto.leader.rebalance.enable=true'. The reblance process spendes too more time and cpu resource. We find that the function:'controllerContext.allPartitions' is invoked too many times. !clipboard_image_1606806581629.png! > Replica leader election is too slow in the case of too many partitions > -- > > Key: KAFKA-10794 > URL: https://issues.apache.org/jira/browse/KAFKA-10794 > Project: Kafka > Issue Type: Improvement > Components: core >Affects Versions: 2.6.0, 2.5.1 >Reporter: limeng >Priority: Major > Attachments: clipboard_image_1606806581629.png > > > There is more than 6000 topics and 300 brokers in my kafka cluster, and we > set the config:'auto.leader.rebalance.enable=true'. > The reblance process spendes too more time and cpu resource. > We find that the function:'controllerContext.allPartitions' is invoked too > many times. > !clipboard_image_1606806581629.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KAFKA-10794) Replica leader election is too slow in the case of too many partitions
limeng created KAFKA-10794: -- Summary: Replica leader election is too slow in the case of too many partitions Key: KAFKA-10794 URL: https://issues.apache.org/jira/browse/KAFKA-10794 Project: Kafka Issue Type: Improvement Components: core Affects Versions: 2.5.1, 2.6.0 Reporter: limeng -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KAFKA-8051) remove KafkaMbean when network close
limeng created KAFKA-8051: - Summary: remove KafkaMbean when network close Key: KAFKA-8051 URL: https://issues.apache.org/jira/browse/KAFKA-8051 Project: Kafka Issue Type: Bug Components: clients, core Affects Versions: 0.10.2.2, 0.10.2.1, 0.10.2.0 Reporter: limeng Fix For: 2.2.1 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)
[jira] [Created] (KAFKA-8050) remove KafkaMbean when network close
limeng created KAFKA-8050: - Summary: remove KafkaMbean when network close Key: KAFKA-8050 URL: https://issues.apache.org/jira/browse/KAFKA-8050 Project: Kafka Issue Type: Bug Components: clients, core Affects Versions: 0.10.2.2, 0.10.2.1, 0.10.2.0 Reporter: limeng Fix For: 2.2.1 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)
[jira] [Created] (KAFKA-8049) remove KafkaMbean when network close
limeng created KAFKA-8049: - Summary: remove KafkaMbean when network close Key: KAFKA-8049 URL: https://issues.apache.org/jira/browse/KAFKA-8049 Project: Kafka Issue Type: Bug Components: clients, core Affects Versions: 0.10.2.2, 0.10.2.1, 0.10.2.0 Reporter: limeng Fix For: 2.2.1 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)
[jira] [Created] (KAFKA-8048) remove KafkaMbean when network close
limeng created KAFKA-8048: - Summary: remove KafkaMbean when network close Key: KAFKA-8048 URL: https://issues.apache.org/jira/browse/KAFKA-8048 Project: Kafka Issue Type: Bug Components: clients, core Affects Versions: 0.10.2.2, 0.10.2.1, 0.10.2.0 Reporter: limeng Fix For: 2.2.1 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)
[jira] [Created] (KAFKA-8047) remove KafkaMbean when network close
limeng created KAFKA-8047: - Summary: 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.2, 0.10.2.1, 0.10.2.0 Reporter: limeng Fix For: 2.2.1 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)
