Skip to content
This repository has been archived by the owner on Jan 8, 2020. It is now read-only.

Deadlock when sarama commit an out of range offset #167

Closed
aravindvs opened this issue Sep 19, 2017 · 3 comments
Closed

Deadlock when sarama commit an out of range offset #167

aravindvs opened this issue Sep 19, 2017 · 3 comments

Comments

@aravindvs
Copy link

aravindvs commented Sep 19, 2017

This is a dup of: #121

Reopening this with data here:
`
I am reopening this one as I saw a similar behavior:
(1) Producer was producing at a much higher rate than the consumer
(2) Consumer was trying to commit offset which is already deleted.

I was able to log the error message as well by listening on consumer.Errors() channel and got this one:
kafka-consumer : Failed to consume message. Error: kafka: error while consuming topic: kafka server: The requested offset is outside the range of offsets maintained by the server for the given topic/partition.
After this since the pc.Loop() above doesn't refresh, which means we will just be stuck as @plopik mentioned above. I think it will be better to just trigger a rebalance() which should get us out of this situation as mentioned earlier.
`

@dim
Copy link
Member

dim commented Sep 21, 2017

@aravindvs can you please test with #169, this should fix you issue once and for all

@aravindvs
Copy link
Author

@dim - Thanks! will definitely try it and let you know.

@dim
Copy link
Member

dim commented Sep 26, 2017

Should be fixed, please re-open if you still experience problems

@dim dim closed this as completed Sep 26, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants