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

Sort (OLDEST) does not work anymore in 0.25.1 --> error in computing/reading the begin offsets #1958

Open
thibthibus opened this issue Sep 27, 2024 · 2 comments
Labels

Comments

@thibthibus
Copy link
Contributor

thibthibus commented Sep 27, 2024

Hi,

There was a change in 0.25.1 ( #1817 ?) that led to an erroneous determination / calculation of the beginning offsets for compacted topics.
As a consequence, one cannot display the messages of a Kafka topic using sort (OLDEST).

AKHQ 0.25.1
image

AKHQ 0.25.0
image

Kafka CLI
image

Thanks for looking at this issue

Thibaut

@AlexisSouquiere
Copy link
Collaborator

Can you elaborate ? You are not able to see any messages for your compacted topic in AKHQ ?
I just tried again and the result that I have on a compacted topic between AKHQ with the sort oldest or a kafka-console-consumer is the exact same.

But with the kafka-get-offsets script (and the same argument as yours), it's giving me 0 for all the partitions (which is wrong) while the first offset of my partitions are 265, 1015 and 563

@thibthibus
Copy link
Contributor Author

Hi @AlexisSouquiere
Sorry for the late reply. Actually we faced another issue which is probably related.
We performed an offset update to earliest on a consumer group. After restart the consumer was not able to consume any message in the topic. After analyze we noticed that the offsets had been set to offsets values that don't exist anymore for the topic.
We compared 0.25.1 (and dev) release with 0.25.0 and noticed that the update offsets to earliest was giving different results. With 0.25.1 the operation was returning older offsets for all partitions.
We could confirm that 0.25.0 is correct as it brings the same results as in Confluent Cloud (where we can now perform this operation).
As a consequence we rolled back all our AKHQ instances to 0.25.0.
Hope this helps,
Regards,
Thibaut

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

No branches or pull requests

2 participants