Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Handle lookup_coordinator send failures #1279

Merged
merged 3 commits into from
Oct 24, 2017
Merged

Conversation

dpkp
Copy link
Owner

@dpkp dpkp commented Oct 24, 2017

Fixes #1278

@jeffwidman
Copy link
Contributor

jeffwidman commented Oct 24, 2017

Wouldn't the Java code hit this? Curious whether there's an upstream Jira ticket...

return self._find_coordinator_future

# If there is an error sending the group coordinator request
# then the errback will immediately fire and reset _find_coordinator_future = None
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be _reset_find_coordinator_future?

If you're actually trying to use "reset" as a verb, can you pick a different word as it makes it confusing since both _find_coordinator_future and _reset_find_coordinator_future are used in this block of code...

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@dpkp
Copy link
Owner Author

dpkp commented Oct 24, 2017

kafka-python does immediate network sends, which exposes futures to immediate failure. Java client uses an asynchronous send queue, so it would not have the same issue. See #981

@dpkp dpkp merged commit d2001e4 into master Oct 24, 2017
@jeffwidman jeffwidman deleted the fast_lookup_coordinator_reset branch October 25, 2017 00:48
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants