Skip to content

Kafka has rebalancing issues #750

Open
@CCTV-six

Description

@CCTV-six

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions