Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kafka has rebalancing issues #750

Open
CCTV-six opened this issue Sep 5, 2024 · 1 comment
Open

Kafka has rebalancing issues #750

CCTV-six opened this issue Sep 5, 2024 · 1 comment

Comments

@CCTV-six
Copy link

CCTV-six commented Sep 5, 2024

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.

@OneCricketeer
Copy link

Are you sure this is an issue with the container and not Kafka itself / the code you've not shared?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants