You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "chao (JIRA)" <ji...@apache.org> on 2016/03/25 08:24:25 UTC
[jira] [Created] (KAFKA-3466) consumer was stuck , and offset can
not be moved
chao created KAFKA-3466:
---------------------------
Summary: consumer was stuck , and offset can not be moved
Key: KAFKA-3466
URL: https://issues.apache.org/jira/browse/KAFKA-3466
Project: Kafka
Issue Type: Bug
Components: kafka streams
Affects Versions: 0.9.0.1
Reporter: chao
Priority: Blocker
We found some strange issue when we upgrade 0.9.0.1 . Some consumer was suck and can not continue to move offset
if we manually commit offset , it will throw the following exception .
1. How does it happen ??
2. If it happen , how we can consumer message and move offset to latest , and continue consume with this group
2016-03-25 14:37:57 DEBUG Metrics:201 - Added sensor with name node-2147483646.bytes-sent
2016-03-25 14:37:57 DEBUG Metrics:201 - Added sensor with name node-2147483646.bytes-received
2016-03-25 14:37:57 DEBUG Metrics:201 - Added sensor with name node-2147483646.latency
2016-03-25 14:37:57 DEBUG NetworkClient:492 - Completed connection to node 2147483646
2016-03-25 14:37:57 ERROR ConsumerCoordinator:544 - Error UNKNOWN_MEMBER_ID occurred while committing offsets for group XX_integration
2016-03-25 14:38:02 DEBUG Metrics:220 - Removed sensor with name connections-closed:client-id-consumer-1
2016-03-25 14:38:02 DEBUG Metrics:220 - Removed sensor with name connections-created:client-id-consumer-1
2016-03-25 14:38:02 DEBUG Metrics:220 - Removed sensor with name bytes-sent-received:client-id-consumer-1
2016-03-25 14:38:02 DEBUG Metrics:220 - Removed sensor with name bytes-received:client-id-consumer-1
2016-03-25 14:38:02 DEBUG Metrics:220 - Removed sensor with name bytes-sent:client-id-consumer-1
2016-03-25 14:38:02 DEBUG Metrics:220 - Removed sensor with name select-time:client-id-consumer-1
2016-03-25 14:38:02 DEBUG Metrics:220 - Removed sensor with name io-time:client-id-consumer-1
2016-03-25 14:38:02 DEBUG Metrics:220 - Removed sensor with name node--3.bytes-sent
2016-03-25 14:38:02 DEBUG Metrics:220 - Removed sensor with name node--3.bytes-received
2016-03-25 14:38:02 DEBUG Metrics:220 - Removed sensor with name node--3.latency
2016-03-25 14:38:02 DEBUG Metrics:220 - Removed sensor with name node-0.bytes-sent
2016-03-25 14:38:02 DEBUG Metrics:220 - Removed sensor with name node-0.bytes-received
2016-03-25 14:38:02 DEBUG Metrics:220 - Removed sensor with name node-0.latency
2016-03-25 14:38:02 DEBUG Metrics:220 - Removed sensor with name node-2147483646.bytes-sent
2016-03-25 14:38:02 DEBUG Metrics:220 - Removed sensor with name node-2147483646.bytes-received
2016-03-25 14:38:02 DEBUG Metrics:220 - Removed sensor with name node-2147483646.latency
2016-03-25 14:38:02 DEBUG KafkaConsumer:1241 - The Kafka consumer has closed.
Exception in thread "main" org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be completed due to group rebalance
at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator$OffsetCommitResponseHandler.handle(ConsumerCoordinator.java:546)
at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator$OffsetCommitResponseHandler.handle(ConsumerCoordinator.java:487)
at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:681)
at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$CoordinatorResponseHandler.onSuccess(AbstractCoordinator.java:654)
at org.apache.kafka.clients.consumer.internals.RequestFuture$1.onSuccess(RequestFuture.java:167)
at org.apache.kafka.clients.consumer.internals.RequestFuture.fireSuccess(RequestFuture.java:133)
at org.apache.kafka.clients.consumer.internals.RequestFuture.complete(RequestFuture.java:107)
at
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)