consumer: broker is still loading offsets after a leader change for that offset's topic partition.

[el-chen]

Versions

Please specify real version numbers or git SHAs, not just "Latest" since that changes fairly regularly.

Sarama	Kafka	Go
Latest	2.3.0	1.12.8

Problem Description

I started 3 consumers using the consumer group example given in Github to consume the data from Kafka 2.3.0. the clients ran well for a few hours and then exited with this error

2019/11/03 04:08:34 Error from consumer: %v kafka server: The broker is still loading offsets after a leader change for that offset's topic partition.

Kafka Logs -
[2019-11-03 04:08:33,306] INFO [ReplicaFetcher replicaId=2, leaderId=3, fetcherId=0] Starting (kafka.server.ReplicaFetcherThread)
[2019-11-03 04:08:33,345] INFO [ReplicaFetcher replicaId=2, leaderId=3, fetcherId=0] Retrying leaderEpoch request for partition checkpoint_avro-9 as the leader reported an error: UNKNOWN_LEADER_EPOCH (kafka.server.ReplicaFetcherThread)
[2019-11-03 04:08:33,345] INFO [ReplicaFetcher replicaId=2, leaderId=3, fetcherId=0] Retrying leaderEpoch request for partition checkpoint_avro-7 as the leader reported an error: UNKNOWN_LEADER_EPOCH (kafka.server.ReplicaFetcherThread)

What will be the problem here?

[ghost]

Thank you for taking the time to raise this issue. However, it has not had any activity on it in the past 90 days and will be closed in 30 days if no updates occur.
Please check if the master branch has already resolved the issue since it was raised. If you believe the issue is still valid and you would like input from the maintainers then please comment to ask for it to be reviewed.

[ruban-rengaraju]

Following up on this, was a fix found?

[madhankumar2024]

can we re-open this issue ? I am having the same issue with producer ? "failed to create kafka producer: "kafka server: The broker is still loading offsets after a leader change for that offset's topic partition""

[dnwe]

@madhankumar2024 for consumers this was believed to have been fixed by #2214

If you're seeing that error on a producer then please open a fresh issue with the details

[madhankumar2024]

@madhankumar2024 for consumers this was believed to have been fixed by #2214

If you're seeing that error on a producer then please open a fresh issue with the details

Thank you @dnwe , I will check with current sarama version that fix is applied or not. and open a new issue if required