Disabling Java DNS cache for Zookeeper ensemble on docker#1
Open
dbaba wants to merge 3 commits intomesoscloud:masterfrom
Open
Disabling Java DNS cache for Zookeeper ensemble on docker#1dbaba wants to merge 3 commits intomesoscloud:masterfrom
dbaba wants to merge 3 commits intomesoscloud:masterfrom
Conversation
Member
|
Hello @dbaba thank you for reporting this issue, I will investigate this issue and get back to you, as I have not experienced this problem previously. |
|
Playing with JVM network cache should not help in this situation much as zookeeper have his own way to deal with this, and there's an issue on that matter that exists from quite some time (https://issues.apache.org/jira/browse/ZOOKEEPER-1506). Should have been released with 3.4.7, but it had a critical bug (a deadlock), so it should be available in 3.4.8. |
|
is this resolved? we are still having issues with that, using |
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
4 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.
I'd found an issue when creating a ZK ensemble with 3 ZK containers (by setting
MYIDandSERVERS) along with dnsdock.The issue is the first of the three containers kept failing to resolve other hosts (UnknownHostException was thrown) which started after the first one is running. This was caused by Java's DNS cache preventing the ZK from performing DNS queries, so I disabled it.
After disabling the DNS cache, ZK ensemble on docker worked fine.
Please consider to review and accept this request if the change is helpful for you as well or discard it otherwise.