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

max.poll.interval.ms: properly handle blocking calls #2365

Merged
merged 1 commit into from
Jun 18, 2019
Merged

Conversation

edenhill
Copy link
Contributor

Previous to this fix the app_polled time was only updated upon
entry to a (possibly) blocking function, such as consumer_poll().
If the call had a timeout > max.poll.interval.ms and there were no messages
for at least max.poll.interval.ms, the max poll check would kick in and
evict the consumer from the group due to inactivity.

We now signal to app_polled that we're in a blocking call
which prevents the max poll check to fire.

Previous to this fix the app_polled time was only updated upon
entry to a (possibly) blocking function, such as consumer_poll().
If the call had a timeout > max.poll.interval.ms and there were no messages
for at least max.poll.interval.ms, the max poll check would kick in and
evict the consumer from the group due to inactivity.

We now signal to app_polled that we're in a blocking call
which prevents the max poll check to fire.
@edenhill edenhill merged commit 4df3672 into master Jun 18, 2019
@edenhill edenhill deleted the maxpoll2 branch June 18, 2019 14:27
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