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

Sync with upstream master #1

Merged
merged 6 commits into from
Apr 18, 2019
Merged

Sync with upstream master #1

merged 6 commits into from
Apr 18, 2019

Conversation

saich
Copy link
Member

@saich saich commented Apr 18, 2019

No description provided.

saich and others added 6 commits April 15, 2019 17:10
…outdated.

Only add ISRs that the cluster is aware of to avoid KeyErrors here.
Inconsistencies will be automatically resolved when `Cluster.update` is called.

The error happens in following use case:
1. KafkaClient is initiated (and thus Cluster is also initiated with cluster's metadata)
2. New brokers has been added to Kafka's cluster and ISRs of some partitions has been rebalanced
3. Try to access a topic using the client object created in step 1 - It **FAILS** because one of the ISRs is in new broker that this client is not aware of yet
`LeaderNotFoundError` while initiating a `Topic` object
Improve stability in cases of new broker additions to cluster
@saich saich merged commit c8c3e44 into Instamojo:master Apr 18, 2019
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