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

Consumer offset management #3

Closed
wants to merge 5 commits into from
Closed

Conversation

eapache
Copy link
Contributor

@eapache eapache commented Jul 30, 2013

@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.

Evan Huus added 5 commits July 30, 2013 12:06
Otherwise we can't tell the difference between no error, and simply not
receiving data for that partition. Also add a GetError helper function.
@tobi
Copy link

tobi commented Jul 31, 2013

Can you file a ticket with Kafka so that they are aware?

  • tobi
    CEO Shopify

On Tue, Jul 30, 2013 at 2:41 PM, Evan Huus notifications@github.com wrote:

@burke https://github.com/burke @airolson https://github.com/airolson
@tobi https://github.com/tobi @fw42 https://github.com/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 #2.

You can merge this Pull Request by running

git pull https://github.com/Shopify/sarama consumer-offset-management

Or view, comment on, or merge it at:

#3
Commit Summary

  • Add a GetBlock helper to the OffsetFetchResponse
  • Fetch the offset when starting a consumer
  • Have OffsetCommitResponse hold pointers to errors
  • Tweaks to fetchOffset
  • Implement Consumer.Commit, Fixes Offset Fetch/Commit Support #2.

File Changes

Patch Links:

@eapache
Copy link
Contributor Author

eapache commented Jul 31, 2013

According to dpkp/kafka-python#18 it may already be fixed in Kafka trunk, I will try that and see.

@eapache
Copy link
Contributor Author

eapache commented Jul 31, 2013

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...

@eapache
Copy link
Contributor Author

eapache commented Jul 31, 2013

Ticket filed with Kafka, maybe we'll get some answers: https://issues.apache.org/jira/browse/KAFKA-993

@eapache
Copy link
Contributor Author

eapache commented Aug 8, 2013

Needs redoing after the refactor.

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.

2 participants