[2.3] Backport mocked HostResolver from KAFKA-12193 to avoid relying on kafka.apache.org for specific DNS behavior - #10055
Closed
gardnervickers wants to merge 1 commit into
Conversation
…ka.apache.org for specific DNS behavior.
gardnervickers
force-pushed
the
backport-host-resolver-KAFKA-12193
branch
from
February 4, 2021 21:03
468dd5a to
2d536a4
Compare
gardnervickers
changed the title
Member
|
Hey @gardnervickers , do you have plans to open a PR against 2.6 as well? Just checking in since it seems this fix has been ported to everything except 2.6 so far and I want to keep track for the 2.6.2 release |
Contributor
Author
|
@ableegoldman I believe @bob-barrett was working on a PR against 2.6. |
Contributor
|
@ableegoldman the 2.6 backport is #10061. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The original PR was #9902
The reason for back-porting this improved test infrastructure is to address some flakes which we have seen when kafka.apache.org DNS changes, specifically in the
ClusterConnectionStatesTest. This change uses a mocked resolver for the multi-ip tests.