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

Nakadi producers does not recover from kafka broker shutdowns #188

Closed
rcillo opened this issue Mar 23, 2016 · 1 comment
Closed

Nakadi producers does not recover from kafka broker shutdowns #188

rcillo opened this issue Mar 23, 2016 · 1 comment
Assignees

Comments

@rcillo
Copy link
Contributor

rcillo commented Mar 23, 2016

Besides periodically refreshing the list of available brokers https://github.com/zalando/nakadi/blob/nakadi-jvm/src/main/java/de/zalando/aruha/nakadi/repository/kafka/KafkaLocationManager.java#L90-L98 Nakadi does not refresh it's producer instances with up-to-date properties (list of brokers).

Since producers are created during initialisation phase only https://github.com/zalando/nakadi/blob/nakadi-jvm/src/main/java/de/zalando/aruha/nakadi/repository/kafka/KafkaFactory.java#L16, they will not use recently created brokers. It may cause inconsistent behaviour when publishing events.

Nakadi should recover from such scenarios by discovering recently created brokers and updating producers with such information.

@rcillo
Copy link
Contributor Author

rcillo commented Apr 29, 2016

This was a false positive. New brokers weren't getting any traffic due to a bug in the rebalancing of buku that was fixed here https://github.com/zalando/saiki-buku/commit/c37624cbd383e8e29257dc8c7716eaee26c10a6a

@rcillo rcillo closed this as completed Apr 29, 2016
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

No branches or pull requests

2 participants