Coordinator selected invalid assignment protocol: null

[sairamlrg]

we are using spring-kafka 1.3.9 version and 0.11.0.2 kafka client in our application.
we have observed the below mentioned error and got flooded with logs in crores.
How can we handle this error , Do we have any exception handler in spring for this ?

In our application, We have spring.kafka.listener.concurrency = 16 and we launch 4 instances of such that. Totally we have 16*4 = 64 consumers with same group id. We also have 64 partitions in kafka topic. From logs we have observered that the error is logged only on one consumer repeatedly consumer -1(thread: 1-c-1)

We encountered this issue thrice till now.

Error Log:

java.lang.IllegalStateException: Coordinator selected invalid assignment protocol: null
at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.onJoinComplete(ConsumerCoordinator.java:218)
at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.joinGroupIfNeeded(AbstractCoordinator.java:367)
at org.apache.kafka.clients.consumer.internals.AbstractCoordinator.ensureActiveGroup(AbstractCoordinator.java:316)
at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.poll(ConsumerCoordinator.java:297)
at org.apache.kafka.clients.consumer.KafkaConsumer.pollOnce(KafkaConsumer.java:1078)
at org.apache.kafka.clients.consumer.KafkaConsumer.poll(KafkaConsumer.java:1043)
at org.springframework.kafka.listener.KafkaMessageListenerContainer$ListenerConsumer.run(KafkaMessageListenerContainer.java:646)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.lang.Thread.run(Thread.java:748)

But we are not able to reproduce the issue again ?
First would like to know ,what are the possibilities of this error ?
How can we handle this error , Do we have any exception handler in spring for this ?

Please help us on this. Thank you.

[artembilan]

See here: #772 (comment)

So, another reporter realized that this is not Spring Kafka problem.
We are not experts how network protocol works in Apache Kafka.

Consider to contact with Apache Kafka community to get some possible answer.

Also this GH issues not for questions like this: only bug reports or improvement requests are acceptable here.

Looks like you are not only one who struggle with the same problem: https://stackoverflow.com/questions/55260410/kafka-streams-cases-where-coordinator-selected-invalid-assignment-protocol-nu

See more info here as well: https://jaceklaskowski.gitbooks.io/apache-kafka/kafka-consumer-internals-ConsumerCoordinator.html

And here is not resolved JIRA: https://issues.apache.org/jira/browse/KAFKA-7263

So, I'm not sure what you would like to get from Spring level as a solution for native Apache Kafka problem.

Thanks for understanding.

[sairamlrg]

Thank you for the info @artembilan . I am closing this issue as this not related to spring.