GitHub user tschuettel opened a pull request:
https://github.com/apache/zookeeper/pull/320
ZOOKEEPER-2614 Port ZOOKEEPER-1576 to branch 3.4
This is a backport of ZOOKEEPER-1576 to the 3.4-line.
When running Zookeeper as an ensemble in a dynamic environment such as
Kubernetes, the DNS entry of a Zookeeper pod is apparently instantly
purged as one of the nodes goes down. This leads to an UnknownHostException
when interacting with the cluster, even though a healthy majority of nodes
is still working.
This behavior is also observed in a firewall situation as described in
ZOOOKEEPER-1576.
This fix catches and logs the UnkownHostException and continues trying the
next node.
Thanks to Vishal Khandelwal for providing the patch.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/DaimlerTSS/zookeeper ZOOKEEPER-2614
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zookeeper/pull/320.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #320
----
commit 67eff1c9984c0081cd36d4f978fcce642362b4b3
Author: Thomas Schüttel <[email protected]>
Date: 2017-07-30T10:50:23Z
ZOOKEEPER-2614 Port ZOOKEEPER-1576 to branch 3.4
This is a backport of ZOOKEEPER-1576 to the 3.4-line.
When running Zookeeper as an ensemble in a dynamic environment such as
Kubernetes, the DNS entry of a Zookeeper pod is apparently instantly
purged as one of the nodes goes down. This leads to an UnknownHostException
when interacting with the cluster, even though a healthy majority of nodes
is still working.
This behavior is also observed in a firewall situation as described in
ZOOOKEEPER-1576.
This fix catches and logs the UnkownHostException and continues trying the
next node.
Thanks to Vishal Khandelwal for providing the patch.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
