-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Improve fault tolerance by handling leadership election and other metadata changes #55
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
Conversation
|
Any feedback is welcomed - however, please don't close this until the integration test suite is ready. |
|
Just did a rebase - tests appear to be passing. Working on additional tests now. (oops - I think GitHub deleted @mrtheb's comments.) |
|
Yes, I am working on that right now. I will also make some of the changes recommended by @mrtheb. |
|
I had opened a ticket for something similar - #40 |
|
hello travis ... knock knock |
|
@jimjh I'm guessing it's not building automatically since the PR can't be merged automatically. Try rebasing |
…, failed_messages - add integration tests for sync producer - add integration tests for async producer w. leadership election - use log.exception
|
How does this look? |
Improve fault tolerance by handling leadership election and other metadata changes Thanks, @jimjh!
|
OH YEAH. |
Inside
client.pysendfails insidebroker_aware, resettopics_to_brokersFailedPayloadsExceptionInside
conn.pysendorrecvfails, set adirtyflagsend, if thedirtyflag is set, reinit connection