Register the broker with its IP address #377
Open
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
Register the broker with its IP address to prevent issues with non-FQDN DNS lookups from Kafka clients running in other containers
This was referenced Aug 3, 2018
This was referenced Dec 3, 2018
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.
We had an issue where our server running docker has hostname "server123" and the FQDN would be "server123.mycompany.com"
When a Kafka client (Java application) running in another container on the same docker host was connecting with the Kafka cluster it was configured to connect to the Kafka cluster using the FQDN. It connected ok, received from Kafka the address of the specific Kafka node to connect to: "server123" which contained no longer the FQDN. This caused the connection to fail as the Kafka client could not resolve a non-FQDN hostname "server123".
Altering the HOSTNAME_COMMAND of the Kafka node to return the IP adress instead of the non-FQDN hostname solved the issue for us.