You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ERROR [Consumer clientId=consumer-group-1, groupId=consumer-group-1] Error while fetching metadata with correlation id 110 : {consumer-group-1-topic-0=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.consumer.internals.Fetcher)
WARN [Consumer clientId=consumer-group-1, groupId=consumer-group-1] Auto-commit of offsets {consumer-group-1-topic-0=OFFSET(-1), ...} failed for group consumer-group-1: Commit cannot be completed since the group has already rebalanced and assigned the partitions to another member. This means that the time between subsequent calls to poll() was longer than the configured max.poll.interval.ms, which typically implies that the poll loop is spending too much time message processing. You can address this either by increasing max.poll.interval.ms or by reducing the maximum size of batches returned in poll() with max.poll.records. (org.apache.kafka.clients.consumer.internals.ConsumerCoordinator)
ExpectedBehavior
Consumers can handle messages stably and trigger unnecessary rebalancing.
The text was updated successfully, but these errors were encountered:
CurrentBehavior
ERROR [Consumer clientId=consumer-group-1, groupId=consumer-group-1] Error while fetching metadata with correlation id 110 : {consumer-group-1-topic-0=LEADER_NOT_AVAILABLE} (org.apache.kafka.clients.consumer.internals.Fetcher)
WARN [Consumer clientId=consumer-group-1, groupId=consumer-group-1] Auto-commit of offsets {consumer-group-1-topic-0=OFFSET(-1), ...} failed for group consumer-group-1: Commit cannot be completed since the group has already rebalanced and assigned the partitions to another member. This means that the time between subsequent calls to poll() was longer than the configured max.poll.interval.ms, which typically implies that the poll loop is spending too much time message processing. You can address this either by increasing max.poll.interval.ms or by reducing the maximum size of batches returned in poll() with max.poll.records. (org.apache.kafka.clients.consumer.internals.ConsumerCoordinator)
ExpectedBehavior
Consumers can handle messages stably and trigger unnecessary rebalancing.
The text was updated successfully, but these errors were encountered: