Downgrade kafka-python to 1.3.4 to prevent DNS spikes when broker doesn't exist #1592
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
masci
changed the title
ofek
approved these changes
May 22, 2018
|
This was fixed in dpkp/kafka-python#1507, which is part of the recently released |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Temporary downgrade
kafka-pythonto version 1.3.4Motivation
We noticed a huge spike in the number of DNS calls coming from the check when a broker listed on the config file doesn't exist. While this is definitely a misconfiguration problem, we want to investigate the spike, reverting to a known state in the meantime.
Review checklist
no-changeloglabel attached