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

Fix block on control messages #1115

Merged
merged 1 commit into from
Jun 14, 2018
Merged

Fix block on control messages #1115

merged 1 commit into from
Jun 14, 2018

Conversation

eapache
Copy link
Contributor

@eapache eapache commented Jun 14, 2018

Move the skip for those block to after the point where we've
parsed/incremented the offset so we don't get stuck on a response
containing only control messages.

Should fix #1106. @FrancoisPoinsot can you please confirm?

Move the skip for those block to after the point where we've
parsed/incremented the offset so we don't get stuck on a response
containing *only* control messages.
@FrancoisPoinsot
Copy link
Contributor

tested against my topic i know trigger this.
works perfectly.
side note: only work if sarama version > v0_11_0_0

@FrancoisPoinsot
Copy link
Contributor

did not search too much for this but when sarama version < v0_11_0_0 we seem to enter at nRecs == 0 l 553 consumer.go and then get false at partialTrailingMessage so we just return and loop again on the same message

@eapache
Copy link
Contributor Author

eapache commented Jun 14, 2018

Since older versions of kafka don't have control messages, I don't believe it's possible to consume them from that version.

@eapache eapache merged commit d020291 into master Jun 14, 2018
@eapache eapache deleted the move-control-check branch June 14, 2018 20:15
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

Successfully merging this pull request may close these issues.

Block when consuming exactly_once topic
2 participants