Allow the coordinator to auto-commit for api_version==0.8.1 #1832
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Raised once in #1594
We're using
api_version=(0, 8, 1)
andenable_auto_commit=True
. This had worked inkafka-python==1.3.5
but fails now inkafka-python==1.4.6
.In 1.3.5 even though the documentation suggested that commits to ZooKeeper is not supported, we could see the commit reflected upon inspection with zkCli.
In 1.4.6 though,
KafkaConsumer
just doesn't function with the above configuration; because the early exit inConsumerCoordinator.poll()
prevents the coordinator from updatingnext_auto_commit_deadline
. This stale value, in turn, causesKafkaConsumer._message_generator()
to preempt the iteration ofself._fetcher
untilconsumer_timeout
is reached.If we allow for 0.8.1 in
ConsumerCoordinator.poll()
, then everything seems fine. Messages are yielded, and commits are written to ZK.This change is