[jira] [Commented] (KAFKA-4355) StreamThread intermittently dies with "Topic not found during partition assignment" when broker restarted
[ https://issues.apache.org/jira/browse/KAFKA-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15687421#comment-15687421 ] Guozhang Wang commented on KAFKA-4355: -- Resolving the ticket as PR 2133 is merged. [~mihbor] please feel free to re-open if this issue happens again in trunk. > StreamThread intermittently dies with "Topic not found during partition > assignment" when broker restarted > - > > Key: KAFKA-4355 > URL: https://issues.apache.org/jira/browse/KAFKA-4355 > Project: Kafka > Issue Type: Bug > Components: streams >Affects Versions: 0.10.1.0, 0.10.0.0 > Environment: kafka 0.10.0.0 > kafka 0.10.1.0 > uname -a > Linux lp02485 4.4.0-34-generic #53~14.04.1-Ubuntu SMP Wed Jul 27 16:56:40 UTC > 2016 x86_64 x86_64 x86_64 GNU/Linux > java -version > java version "1.8.0_92" > Java(TM) SE Runtime Environment (build 1.8.0_92-b14) > Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode) >Reporter: Michal Borowiecki >Assignee: Eno Thereska > Labels: architecture > Fix For: 0.10.2.0 > > > When (a) starting kafka streams app before the broker or > (b) restarting the broker while the streams app is running: > the stream thread intermittently dies with "Topic not found during partition > assignment" StreamsException. > This happens about between one in 5 or one in 10 times. > Stack trace: > {noformat} > Exception in thread "StreamThread-2" > org.apache.kafka.streams.errors.StreamsException: Topic not found during > partition assignment: scheduler > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.maxNumPartitions(DefaultPartitionGrouper.java:81) > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.partitionGroups(DefaultPartitionGrouper.java:55) > at > org.apache.kafka.streams.processor.internals.StreamPartitionAssignor.assign(StreamPartitionAssignor.java:370) > at > org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.performAssignment(ConsumerCoordinator.java:313) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.onJoinLeader(AbstractCoordinator.java:467) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.access$1000(AbstractCoordinator.java:88) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:419) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:395) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:742) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:722) > at > org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(RequestFuture.java:186) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(RequestFuture.java:149) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.complete(RequestFuture.java:116) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient$RequestFutureCompletionHandler.fireCompletion(ConsumerNetworkClient.java:479) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.firePendingCompletedRequests(ConsumerNetworkClient.java:316) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:256) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:180) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:308) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureActiveGroup(AbstractCoordinator.java:277) > at > org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.poll(ConsumerCoordinator.java:259) > at > org.apache.kafka.clients.consumer.KafkaConsumer.pollOnce(KafkaConsumer.java:1013) > at > org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:979) > at > org.apache.kafka.streams.processor.internals.StreamThread.runLoop(StreamThread.java:407) > at > org.apache.kafka.streams.processor.internals.StreamThread.run(StreamThread.java:242) > {noformat} > Our app has 2 streams in it, consuming from 2 different topics. > Sometimes the exception happens on both stream threads. Sometimes only on one > of the stream threads. > The exception is preceded by: > {noformat} > [2016-10-28 16:17:55,239] INFO [StreamThread-2] (Re-)joining group >
[jira] [Commented] (KAFKA-4355) StreamThread intermittently dies with "Topic not found during partition assignment" when broker restarted
[ https://issues.apache.org/jira/browse/KAFKA-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15687416#comment-15687416 ] ASF GitHub Bot commented on KAFKA-4355: --- Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/2133 > StreamThread intermittently dies with "Topic not found during partition > assignment" when broker restarted > - > > Key: KAFKA-4355 > URL: https://issues.apache.org/jira/browse/KAFKA-4355 > Project: Kafka > Issue Type: Bug > Components: streams >Affects Versions: 0.10.1.0, 0.10.0.0 > Environment: kafka 0.10.0.0 > kafka 0.10.1.0 > uname -a > Linux lp02485 4.4.0-34-generic #53~14.04.1-Ubuntu SMP Wed Jul 27 16:56:40 UTC > 2016 x86_64 x86_64 x86_64 GNU/Linux > java -version > java version "1.8.0_92" > Java(TM) SE Runtime Environment (build 1.8.0_92-b14) > Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode) >Reporter: Michal Borowiecki >Assignee: Eno Thereska > Labels: architecture > > When (a) starting kafka streams app before the broker or > (b) restarting the broker while the streams app is running: > the stream thread intermittently dies with "Topic not found during partition > assignment" StreamsException. > This happens about between one in 5 or one in 10 times. > Stack trace: > {noformat} > Exception in thread "StreamThread-2" > org.apache.kafka.streams.errors.StreamsException: Topic not found during > partition assignment: scheduler > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.maxNumPartitions(DefaultPartitionGrouper.java:81) > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.partitionGroups(DefaultPartitionGrouper.java:55) > at > org.apache.kafka.streams.processor.internals.StreamPartitionAssignor.assign(StreamPartitionAssignor.java:370) > at > org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.performAssignment(ConsumerCoordinator.java:313) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.onJoinLeader(AbstractCoordinator.java:467) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.access$1000(AbstractCoordinator.java:88) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:419) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:395) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:742) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:722) > at > org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(RequestFuture.java:186) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(RequestFuture.java:149) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.complete(RequestFuture.java:116) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient$RequestFutureCompletionHandler.fireCompletion(ConsumerNetworkClient.java:479) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.firePendingCompletedRequests(ConsumerNetworkClient.java:316) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:256) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:180) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:308) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureActiveGroup(AbstractCoordinator.java:277) > at > org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.poll(ConsumerCoordinator.java:259) > at > org.apache.kafka.clients.consumer.KafkaConsumer.pollOnce(KafkaConsumer.java:1013) > at > org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:979) > at > org.apache.kafka.streams.processor.internals.StreamThread.runLoop(StreamThread.java:407) > at > org.apache.kafka.streams.processor.internals.StreamThread.run(StreamThread.java:242) > {noformat} > Our app has 2 streams in it, consuming from 2 different topics. > Sometimes the exception happens on both stream threads. Sometimes only on one > of the stream threads. > The exception is preceded by: > {noformat} > [2016-10-28 16:17:55,239] INFO [StreamThread-2] (Re-)joining group > pool-scheduler >
[jira] [Commented] (KAFKA-4355) StreamThread intermittently dies with "Topic not found during partition assignment" when broker restarted
[ https://issues.apache.org/jira/browse/KAFKA-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15676554#comment-15676554 ] ASF GitHub Bot commented on KAFKA-4355: --- Github user enothereska closed the pull request at: https://github.com/apache/kafka/pull/2133 > StreamThread intermittently dies with "Topic not found during partition > assignment" when broker restarted > - > > Key: KAFKA-4355 > URL: https://issues.apache.org/jira/browse/KAFKA-4355 > Project: Kafka > Issue Type: Bug > Components: streams >Affects Versions: 0.10.1.0, 0.10.0.0 > Environment: kafka 0.10.0.0 > kafka 0.10.1.0 > uname -a > Linux lp02485 4.4.0-34-generic #53~14.04.1-Ubuntu SMP Wed Jul 27 16:56:40 UTC > 2016 x86_64 x86_64 x86_64 GNU/Linux > java -version > java version "1.8.0_92" > Java(TM) SE Runtime Environment (build 1.8.0_92-b14) > Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode) >Reporter: Michal Borowiecki >Assignee: Eno Thereska > Labels: architecture > > When (a) starting kafka streams app before the broker or > (b) restarting the broker while the streams app is running: > the stream thread intermittently dies with "Topic not found during partition > assignment" StreamsException. > This happens about between one in 5 or one in 10 times. > Stack trace: > {noformat} > Exception in thread "StreamThread-2" > org.apache.kafka.streams.errors.StreamsException: Topic not found during > partition assignment: scheduler > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.maxNumPartitions(DefaultPartitionGrouper.java:81) > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.partitionGroups(DefaultPartitionGrouper.java:55) > at > org.apache.kafka.streams.processor.internals.StreamPartitionAssignor.assign(StreamPartitionAssignor.java:370) > at > org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.performAssignment(ConsumerCoordinator.java:313) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.onJoinLeader(AbstractCoordinator.java:467) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.access$1000(AbstractCoordinator.java:88) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:419) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:395) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:742) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:722) > at > org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(RequestFuture.java:186) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(RequestFuture.java:149) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.complete(RequestFuture.java:116) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient$RequestFutureCompletionHandler.fireCompletion(ConsumerNetworkClient.java:479) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.firePendingCompletedRequests(ConsumerNetworkClient.java:316) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:256) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:180) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:308) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureActiveGroup(AbstractCoordinator.java:277) > at > org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.poll(ConsumerCoordinator.java:259) > at > org.apache.kafka.clients.consumer.KafkaConsumer.pollOnce(KafkaConsumer.java:1013) > at > org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:979) > at > org.apache.kafka.streams.processor.internals.StreamThread.runLoop(StreamThread.java:407) > at > org.apache.kafka.streams.processor.internals.StreamThread.run(StreamThread.java:242) > {noformat} > Our app has 2 streams in it, consuming from 2 different topics. > Sometimes the exception happens on both stream threads. Sometimes only on one > of the stream threads. > The exception is preceded by: > {noformat} > [2016-10-28 16:17:55,239] INFO [StreamThread-2] (Re-)joining group > pool-scheduler >
[jira] [Commented] (KAFKA-4355) StreamThread intermittently dies with "Topic not found during partition assignment" when broker restarted
[ https://issues.apache.org/jira/browse/KAFKA-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15676555#comment-15676555 ] ASF GitHub Bot commented on KAFKA-4355: --- GitHub user enothereska reopened a pull request: https://github.com/apache/kafka/pull/2133 KAFKA-4355: Skip topics that have no partitions You can merge this pull request into a Git repository by running: $ git pull https://github.com/enothereska/kafka KAFKA-4355-topic-not-found Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2133.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2133 commit 6acb95f2da291072f20b92b47bd078a47922c2e5 Author: Eno ThereskaDate: 2016-11-15T10:03:21Z Skip topics that have no partitions commit 3a0a5b0f4385aebe0c7adfbdc781cd265ea3729a Author: Eno Thereska Date: 2016-11-18T10:17:50Z Added a test > StreamThread intermittently dies with "Topic not found during partition > assignment" when broker restarted > - > > Key: KAFKA-4355 > URL: https://issues.apache.org/jira/browse/KAFKA-4355 > Project: Kafka > Issue Type: Bug > Components: streams >Affects Versions: 0.10.1.0, 0.10.0.0 > Environment: kafka 0.10.0.0 > kafka 0.10.1.0 > uname -a > Linux lp02485 4.4.0-34-generic #53~14.04.1-Ubuntu SMP Wed Jul 27 16:56:40 UTC > 2016 x86_64 x86_64 x86_64 GNU/Linux > java -version > java version "1.8.0_92" > Java(TM) SE Runtime Environment (build 1.8.0_92-b14) > Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode) >Reporter: Michal Borowiecki >Assignee: Eno Thereska > Labels: architecture > > When (a) starting kafka streams app before the broker or > (b) restarting the broker while the streams app is running: > the stream thread intermittently dies with "Topic not found during partition > assignment" StreamsException. > This happens about between one in 5 or one in 10 times. > Stack trace: > {noformat} > Exception in thread "StreamThread-2" > org.apache.kafka.streams.errors.StreamsException: Topic not found during > partition assignment: scheduler > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.maxNumPartitions(DefaultPartitionGrouper.java:81) > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.partitionGroups(DefaultPartitionGrouper.java:55) > at > org.apache.kafka.streams.processor.internals.StreamPartitionAssignor.assign(StreamPartitionAssignor.java:370) > at > org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.performAssignment(ConsumerCoordinator.java:313) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.onJoinLeader(AbstractCoordinator.java:467) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.access$1000(AbstractCoordinator.java:88) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:419) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:395) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:742) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:722) > at > org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(RequestFuture.java:186) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(RequestFuture.java:149) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.complete(RequestFuture.java:116) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient$RequestFutureCompletionHandler.fireCompletion(ConsumerNetworkClient.java:479) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.firePendingCompletedRequests(ConsumerNetworkClient.java:316) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:256) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:180) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:308) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureActiveGroup(AbstractCoordinator.java:277) > at >
[jira] [Commented] (KAFKA-4355) StreamThread intermittently dies with "Topic not found during partition assignment" when broker restarted
[ https://issues.apache.org/jira/browse/KAFKA-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15666719#comment-15666719 ] ASF GitHub Bot commented on KAFKA-4355: --- GitHub user enothereska opened a pull request: https://github.com/apache/kafka/pull/2133 KAFKA-4355: Skip topics that have no partitions You can merge this pull request into a Git repository by running: $ git pull https://github.com/enothereska/kafka KAFKA-4355-topic-not-found Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/2133.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2133 commit 6acb95f2da291072f20b92b47bd078a47922c2e5 Author: Eno ThereskaDate: 2016-11-15T10:03:21Z Skip topics that have no partitions > StreamThread intermittently dies with "Topic not found during partition > assignment" when broker restarted > - > > Key: KAFKA-4355 > URL: https://issues.apache.org/jira/browse/KAFKA-4355 > Project: Kafka > Issue Type: Bug > Components: streams >Affects Versions: 0.10.1.0, 0.10.0.0 > Environment: kafka 0.10.0.0 > kafka 0.10.1.0 > uname -a > Linux lp02485 4.4.0-34-generic #53~14.04.1-Ubuntu SMP Wed Jul 27 16:56:40 UTC > 2016 x86_64 x86_64 x86_64 GNU/Linux > java -version > java version "1.8.0_92" > Java(TM) SE Runtime Environment (build 1.8.0_92-b14) > Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode) >Reporter: Michal Borowiecki >Assignee: Eno Thereska > Labels: architecture > > When (a) starting kafka streams app before the broker or > (b) restarting the broker while the streams app is running: > the stream thread intermittently dies with "Topic not found during partition > assignment" StreamsException. > This happens about between one in 5 or one in 10 times. > Stack trace: > {noformat} > Exception in thread "StreamThread-2" > org.apache.kafka.streams.errors.StreamsException: Topic not found during > partition assignment: scheduler > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.maxNumPartitions(DefaultPartitionGrouper.java:81) > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.partitionGroups(DefaultPartitionGrouper.java:55) > at > org.apache.kafka.streams.processor.internals.StreamPartitionAssignor.assign(StreamPartitionAssignor.java:370) > at > org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.performAssignment(ConsumerCoordinator.java:313) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.onJoinLeader(AbstractCoordinator.java:467) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.access$1000(AbstractCoordinator.java:88) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:419) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:395) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:742) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:722) > at > org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(RequestFuture.java:186) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(RequestFuture.java:149) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.complete(RequestFuture.java:116) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient$RequestFutureCompletionHandler.fireCompletion(ConsumerNetworkClient.java:479) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.firePendingCompletedRequests(ConsumerNetworkClient.java:316) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:256) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:180) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:308) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureActiveGroup(AbstractCoordinator.java:277) > at > org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.poll(ConsumerCoordinator.java:259) > at >
[jira] [Commented] (KAFKA-4355) StreamThread intermittently dies with "Topic not found during partition assignment" when broker restarted
[ https://issues.apache.org/jira/browse/KAFKA-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15628442#comment-15628442 ] Michal Borowiecki commented on KAFKA-4355: -- KAFKA-4366 created for the KafkaSteams.close() hanging issue. > StreamThread intermittently dies with "Topic not found during partition > assignment" when broker restarted > - > > Key: KAFKA-4355 > URL: https://issues.apache.org/jira/browse/KAFKA-4355 > Project: Kafka > Issue Type: Bug > Components: streams >Affects Versions: 0.10.1.0, 0.10.0.0 > Environment: kafka 0.10.0.0 > kafka 0.10.1.0 > uname -a > Linux lp02485 4.4.0-34-generic #53~14.04.1-Ubuntu SMP Wed Jul 27 16:56:40 UTC > 2016 x86_64 x86_64 x86_64 GNU/Linux > java -version > java version "1.8.0_92" > Java(TM) SE Runtime Environment (build 1.8.0_92-b14) > Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode) >Reporter: Michal Borowiecki >Assignee: Guozhang Wang > > When (a) starting kafka streams app before the broker or > (b) restarting the broker while the streams app is running: > the stream thread intermittently dies with "Topic not found during partition > assignment" StreamsException. > This happens about between one in 5 or one in 10 times. > Stack trace: > {noformat} > Exception in thread "StreamThread-2" > org.apache.kafka.streams.errors.StreamsException: Topic not found during > partition assignment: scheduler > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.maxNumPartitions(DefaultPartitionGrouper.java:81) > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.partitionGroups(DefaultPartitionGrouper.java:55) > at > org.apache.kafka.streams.processor.internals.StreamPartitionAssignor.assign(StreamPartitionAssignor.java:370) > at > org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.performAssignment(ConsumerCoordinator.java:313) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.onJoinLeader(AbstractCoordinator.java:467) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.access$1000(AbstractCoordinator.java:88) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:419) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:395) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:742) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:722) > at > org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(RequestFuture.java:186) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(RequestFuture.java:149) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.complete(RequestFuture.java:116) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient$RequestFutureCompletionHandler.fireCompletion(ConsumerNetworkClient.java:479) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.firePendingCompletedRequests(ConsumerNetworkClient.java:316) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:256) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:180) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:308) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureActiveGroup(AbstractCoordinator.java:277) > at > org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.poll(ConsumerCoordinator.java:259) > at > org.apache.kafka.clients.consumer.KafkaConsumer.pollOnce(KafkaConsumer.java:1013) > at > org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:979) > at > org.apache.kafka.streams.processor.internals.StreamThread.runLoop(StreamThread.java:407) > at > org.apache.kafka.streams.processor.internals.StreamThread.run(StreamThread.java:242) > {noformat} > Our app has 2 streams in it, consuming from 2 different topics. > Sometimes the exception happens on both stream threads. Sometimes only on one > of the stream threads. > The exception is preceded by: > {noformat} > [2016-10-28 16:17:55,239] INFO [StreamThread-2] (Re-)joining group > pool-scheduler > (org.apache.kafka.clients.consumer.internals.AbstractCoordinator) > [2016-10-28 16:17:55,240] INFO
[jira] [Commented] (KAFKA-4355) StreamThread intermittently dies with "Topic not found during partition assignment" when broker restarted
[ https://issues.apache.org/jira/browse/KAFKA-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15618009#comment-15618009 ] Michal Borowiecki commented on KAFKA-4355: -- Trying to work around this issue by calling System.exit from the UncaughtExceptionHandler (once the app dies, it will be re-started by our infrastructure). We are adding a shutdown hook as per example here: http://www.confluent.io/blog/introducing-kafka-streams-stream-processing-made-simple/ {code:java} Runtime.getRuntime().addShutdownHook(new Thread(schedulerStreams::close)); {code} However, even though both stream threads report completion of shutdown: {noformat} [2016-10-29 12:32:10,616] INFO [StreamThread-2] stream-thread [StreamThread-2] Stream thread shutdown complete (org.apache.kafka.streams.processor.internals.StreamThread) [2016-10-29 12:32:20,490] INFO [StreamThread-1] stream-thread [StreamThread-1] Stream thread shutdown complete (org.apache.kafka.streams.processor.internals.StreamThread) {noformat} and before that report the closing of their producers and consumers, the app is not stopped. At least the following 2 threads remain active and keep logging: {noformat} [2016-10-29 12:37:05,625] DEBUG [main-SendThread(localhost:19374)] Got ping response for sessionid: 0x158101fc9590021 after 0ms (org.apache.zookeeper.ClientCnxn) [2016-10-29 12:37:09,815] DEBUG [kafka-producer-network-thread | producer-1] Sending metadata request {topics=[scheduler]} to node 0 (org.apache.kafka.clients.NetworkClient) [2016-10-29 12:37:09,818] DEBUG [kafka-producer-network-thread | producer-1] Updated cluster metadata version 15 to Cluster(id = enenZ_SbQKaRlOyJKQMn_g, nodes = [lp02485.openbet:19373 (id: 0 rack: null)], partitions = [Partition(topic = scheduler, partition = 0, leader = 0, replicas = [0,], isr = [0,])]) (org.apache.kafka.clients.Metadata) [2016-10-29 12:37:12,945] DEBUG [main-SendThread(localhost:19374)] Got ping response for sessionid: 0x158101fc9590022 after 0ms (org.apache.zookeeper.ClientCnxn) {noformat} "Stopped Kafka Stream process" is never logged, so the close method remains blocked on the join here, I suspect: https://github.com/apache/kafka/blob/e876df8b37fc6ea54b0a0571306c4a833c919cda/streams/src/main/java/org/apache/kafka/streams/KafkaStreams.java#L227 > StreamThread intermittently dies with "Topic not found during partition > assignment" when broker restarted > - > > Key: KAFKA-4355 > URL: https://issues.apache.org/jira/browse/KAFKA-4355 > Project: Kafka > Issue Type: Bug > Components: streams >Affects Versions: 0.10.1.0, 0.10.0.0 > Environment: kafka 0.10.0.0 > kafka 0.10.1.0 > uname -a > Linux lp02485 4.4.0-34-generic #53~14.04.1-Ubuntu SMP Wed Jul 27 16:56:40 UTC > 2016 x86_64 x86_64 x86_64 GNU/Linux > java -version > java version "1.8.0_92" > Java(TM) SE Runtime Environment (build 1.8.0_92-b14) > Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode) >Reporter: Michal Borowiecki >Assignee: Guozhang Wang > > When (a) starting kafka streams app before the broker or > (b) restarting the broker while the streams app is running: > the stream thread intermittently dies with "Topic not found during partition > assignment" StreamsException. > This happens about between one in 5 or one in 10 times. > Stack trace: > {noformat} > Exception in thread "StreamThread-2" > org.apache.kafka.streams.errors.StreamsException: Topic not found during > partition assignment: scheduler > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.maxNumPartitions(DefaultPartitionGrouper.java:81) > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.partitionGroups(DefaultPartitionGrouper.java:55) > at > org.apache.kafka.streams.processor.internals.StreamPartitionAssignor.assign(StreamPartitionAssignor.java:370) > at > org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.performAssignment(ConsumerCoordinator.java:313) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.onJoinLeader(AbstractCoordinator.java:467) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.access$1000(AbstractCoordinator.java:88) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:419) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:395) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:742) > at >
[jira] [Commented] (KAFKA-4355) StreamThread intermittently dies with "Topic not found during partition assignment" when broker restarted
[ https://issues.apache.org/jira/browse/KAFKA-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15616185#comment-15616185 ] Guozhang Wang commented on KAFKA-4355: -- [~mihbor] Thanks for reporting this. A first note is that in {{Metadata}}, the {{topics}} set and {{cluster}} object are used in different ways: {{topics}} maintains all the topics that this client is interested in (for fetching, or producing), and the {{cluster}} object contains the metadata information obtained from the brokers. So it is possible that topic {{scheduler}} is in the {{topics}} set, indicating that the embedded consumer of the streams client is interested in fetching from this topic, whereas {{cluster}} does not have this topic in its map, indicating that this broker does not know this topic, probably because the brokers hosting this topic is not available during that period of time. As for Streams, I think it should not throw an exception and fail when seeing this situation since it is likely to be transient, instead it could just move forward without assigning this topic any more, and expecting another rebalance to be triggered when this topic is back to be available. Will fix this logic in {{DefaultPartitionGrouper}} for this JIRA. > StreamThread intermittently dies with "Topic not found during partition > assignment" when broker restarted > - > > Key: KAFKA-4355 > URL: https://issues.apache.org/jira/browse/KAFKA-4355 > Project: Kafka > Issue Type: Bug > Components: streams >Affects Versions: 0.10.1.0, 0.10.0.0 > Environment: kafka 0.10.0.0 > kafka 0.10.1.0 > uname -a > Linux lp02485 4.4.0-34-generic #53~14.04.1-Ubuntu SMP Wed Jul 27 16:56:40 UTC > 2016 x86_64 x86_64 x86_64 GNU/Linux > java -version > java version "1.8.0_92" > Java(TM) SE Runtime Environment (build 1.8.0_92-b14) > Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode) >Reporter: Michal Borowiecki >Assignee: Guozhang Wang > > When (a) starting kafka streams app before the broker or > (b) restarting the broker while the streams app is running: > the stream thread intermittently dies with "Topic not found during partition > assignment" StreamsException. > This happens about between one in 5 or one in 10 times. > Stack trace: > {noformat} > Exception in thread "StreamThread-2" > org.apache.kafka.streams.errors.StreamsException: Topic not found during > partition assignment: scheduler > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.maxNumPartitions(DefaultPartitionGrouper.java:81) > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.partitionGroups(DefaultPartitionGrouper.java:55) > at > org.apache.kafka.streams.processor.internals.StreamPartitionAssignor.assign(StreamPartitionAssignor.java:370) > at > org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.performAssignment(ConsumerCoordinator.java:313) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.onJoinLeader(AbstractCoordinator.java:467) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.access$1000(AbstractCoordinator.java:88) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:419) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:395) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:742) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:722) > at > org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(RequestFuture.java:186) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(RequestFuture.java:149) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.complete(RequestFuture.java:116) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient$RequestFutureCompletionHandler.fireCompletion(ConsumerNetworkClient.java:479) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.firePendingCompletedRequests(ConsumerNetworkClient.java:316) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:256) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:180) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:308) > at >
[jira] [Commented] (KAFKA-4355) StreamThread intermittently dies with "Topic not found during partition assignment" when broker restarted
[ https://issues.apache.org/jira/browse/KAFKA-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15616118#comment-15616118 ] Michal Borowiecki commented on KAFKA-4355: -- Perhaps the DefultPartitionGrouper here: https://github.com/apache/kafka/blob/e7663a306f40e9fcbc3096d17fb0f99fa3d11d1d/streams/src/main/java/org/apache/kafka/streams/processor/DefaultPartitionGrouper.java#L81 should instead of StreamsException throw a RetriableException? AbstractCoordinator would then keep looping instead of re-throwing it: https://github.com/apache/kafka/blob/d092673838173d9dedbf5acf3f4e2cd8c736294f/clients/src/main/java/org/apache/kafka/clients/consumer/internals/AbstractCoordinator.java#L320 > StreamThread intermittently dies with "Topic not found during partition > assignment" when broker restarted > - > > Key: KAFKA-4355 > URL: https://issues.apache.org/jira/browse/KAFKA-4355 > Project: Kafka > Issue Type: Bug > Components: streams >Affects Versions: 0.10.1.0, 0.10.0.0 > Environment: kafka 0.10.0.0 > kafka 0.10.1.0 > uname -a > Linux lp02485 4.4.0-34-generic #53~14.04.1-Ubuntu SMP Wed Jul 27 16:56:40 UTC > 2016 x86_64 x86_64 x86_64 GNU/Linux > java -version > java version "1.8.0_92" > Java(TM) SE Runtime Environment (build 1.8.0_92-b14) > Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode) >Reporter: Michal Borowiecki >Assignee: Guozhang Wang > > When (a) starting kafka streams app before the broker or > (b) restarting the broker while the streams app is running: > the stream thread intermittently dies with "Topic not found during partition > assignment" StreamsException. > This happens about between one in 5 or one in 10 times. > Stack trace: > {noformat} > Exception in thread "StreamThread-2" > org.apache.kafka.streams.errors.StreamsException: Topic not found during > partition assignment: scheduler > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.maxNumPartitions(DefaultPartitionGrouper.java:81) > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.partitionGroups(DefaultPartitionGrouper.java:55) > at > org.apache.kafka.streams.processor.internals.StreamPartitionAssignor.assign(StreamPartitionAssignor.java:370) > at > org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.performAssignment(ConsumerCoordinator.java:313) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.onJoinLeader(AbstractCoordinator.java:467) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.access$1000(AbstractCoordinator.java:88) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:419) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:395) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:742) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:722) > at > org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(RequestFuture.java:186) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(RequestFuture.java:149) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.complete(RequestFuture.java:116) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient$RequestFutureCompletionHandler.fireCompletion(ConsumerNetworkClient.java:479) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.firePendingCompletedRequests(ConsumerNetworkClient.java:316) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:256) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:180) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:308) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureActiveGroup(AbstractCoordinator.java:277) > at > org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.poll(ConsumerCoordinator.java:259) > at > org.apache.kafka.clients.consumer.KafkaConsumer.pollOnce(KafkaConsumer.java:1013) > at > org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:979) > at > org.apache.kafka.streams.processor.internals.StreamThread.runLoop(StreamThread.java:407) > at >
[jira] [Commented] (KAFKA-4355) StreamThread intermittently dies with "Topic not found during partition assignment" when broker restarted
[ https://issues.apache.org/jira/browse/KAFKA-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15615967#comment-15615967 ] Michal Borowiecki commented on KAFKA-4355: -- My first suspect so far is the ConsumerCoordinator. In this line: https://github.com/apache/kafka/blob/d092673838173d9dedbf5acf3f4e2cd8c736294f/clients/src/main/java/org/apache/kafka/clients/consumer/internals/ConsumerCoordinator.java#L301 it sets topics on the metadata from subscriptions, which the debugger shows to contain the correct topic name. 4 lines later: https://github.com/apache/kafka/blob/d092673838173d9dedbf5acf3f4e2cd8c736294f/clients/src/main/java/org/apache/kafka/clients/consumer/internals/ConsumerCoordinator.java#L305 it calls client.ensureFreshMetadata(), which can override the topics list. Debugger shows that in the problematic case in https://github.com/apache/kafka/blob/d092673838173d9dedbf5acf3f4e2cd8c736294f/clients/src/main/java/org/apache/kafka/clients/consumer/internals/ConsumerCoordinator.java#L313 the passed metadata object already has an empty set of topics, while the subscriptions object contains the topic name. So I think the topic was removed from the metadata in line 305. > StreamThread intermittently dies with "Topic not found during partition > assignment" when broker restarted > - > > Key: KAFKA-4355 > URL: https://issues.apache.org/jira/browse/KAFKA-4355 > Project: Kafka > Issue Type: Bug > Components: streams >Affects Versions: 0.10.1.0, 0.10.0.0 > Environment: kafka 0.10.0.0 > kafka 0.10.1.0 > uname -a > Linux lp02485 4.4.0-34-generic #53~14.04.1-Ubuntu SMP Wed Jul 27 16:56:40 UTC > 2016 x86_64 x86_64 x86_64 GNU/Linux > java -version > java version "1.8.0_92" > Java(TM) SE Runtime Environment (build 1.8.0_92-b14) > Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode) >Reporter: Michal Borowiecki >Assignee: Guozhang Wang > > When (a) starting kafka streams app before the broker or > (b) restarting the broker while the streams app is running: > the stream thread intermittently dies with "Topic not found during partition > assignment" StreamsException. > This happens about between one in 5 or one in 10 times. > Stack trace: > {noformat} > Exception in thread "StreamThread-2" > org.apache.kafka.streams.errors.StreamsException: Topic not found during > partition assignment: scheduler > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.maxNumPartitions(DefaultPartitionGrouper.java:81) > at > org.apache.kafka.streams.processor.DefaultPartitionGrouper.partitionGroups(DefaultPartitionGrouper.java:55) > at > org.apache.kafka.streams.processor.internals.StreamPartitionAssignor.assign(StreamPartitionAssignor.java:370) > at > org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.performAssignment(ConsumerCoordinator.java:313) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.onJoinLeader(AbstractCoordinator.java:467) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.access$1000(AbstractCoordinator.java:88) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:419) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$JoinGroupResponseHandler.handle(AbstractCoordinator.java:395) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:742) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:722) > at > org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(RequestFuture.java:186) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(RequestFuture.java:149) > at > org.apache.kafka.clients.consumer.internals.RequestFuture.complete(RequestFuture.java:116) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient$RequestFutureCompletionHandler.fireCompletion(ConsumerNetworkClient.java:479) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.firePendingCompletedRequests(ConsumerNetworkClient.java:316) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:256) > at > org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:180) > at > org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:308) > at >