zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2614) Port ZOOKEEPER-1576 to branch3.4
Date Sun, 30 Jul 2017 11:12:02 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16106451#comment-16106451
] 

ASF GitHub Bot commented on ZOOKEEPER-2614:
-------------------------------------------

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 <thomas.schuettel@daimler.com>
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.

----


> Port ZOOKEEPER-1576 to branch3.4
> --------------------------------
>
>                 Key: ZOOKEEPER-2614
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2614
>             Project: ZooKeeper
>          Issue Type: Bug
>    Affects Versions: 3.4.9
>            Reporter: Vishal Khandelwal
>            Assignee: Vishal Khandelwal
>             Fix For: 3.4.11
>
>         Attachments: ZOOKEEPER-2614.branch-3.4.00.patch
>
>
> ZOOKEEPER-1576 handles UnknownHostException and it good to have this change for 3.4 branch
as well. Porting the changes to 3.4 after resolving the conflicts



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message