-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Consumer offset management #3
Conversation
Otherwise we can't tell the difference between no error, and simply not receiving data for that partition. Also add a GetError helper function.
Can you file a ticket with Kafka so that they are aware?
On Tue, Jul 30, 2013 at 2:41 PM, Evan Huus notifications@github.com wrote:
|
According to dpkp/kafka-python#18 it may already be fixed in Kafka trunk, I will try that and see. |
So according to https://issues.apache.org/jira/browse/KAFKA-852 "The Offset fetch/commit APIs are not slated for the 0.8 release". They're only going to be in 0.8.1? I'm confused... |
Ticket filed with Kafka, maybe we'll get some answers: https://issues.apache.org/jira/browse/KAFKA-993 |
Needs redoing after the refactor. |
…tric-backport Add requests-in-flight metric
@burke @airolson @tobi @fw42
This doesn't actually work with the Kafka 0.8 beta yet. It seems to misinterpret the OffsetCommit request messages somehow and ends up underflowing a buffer and disconnecting.
However, I've double-checked the bytes-on-the-wire with Wireshark and the code does produce the correct message according to the spec, so that's their bug (the python client has the same problem).
Fixes issue #2.