Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
Date: Tue, 25 Jul 2017 19:05:00 +0000 (UTC)
From: =?utf-8?Q?Thomas_Sch=C3=BCttel_=28JIRA=29?= <jira@apache.org>
To: dev@zookeeper.apache.org
Message-ID: <JIRA.13011588.1476255751000.10746.1501009500246@Atlassian.JIRA>
In-Reply-To: <JIRA.13011588.1476255751000@Atlassian.JIRA>
References: <JIRA.13011588.1476255751000@Atlassian.JIRA> <JIRA.13011588.1476255751425@jira-lw-us.apache.org>
Subject: [jira] [Commented] (ZOOKEEPER-2614) Port ZOOKEEPER-1576 to
 branch3.4
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 25 Jul 2017 19:05:05 -0000


    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2614?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
16100569#comment-16100569 ]=20

Thomas Sch=C3=BCttel commented on ZOOKEEPER-2614:
--------------------------------------------

I just tested the patch with my Zookeeper ensemble running in Kubernetes. I=
t was works fine now. Previously without the patch, my Kafka-cluster failed=
 as soon as one Zookeeper node died even though a healthy ensemble was stil=
l present.
Please merge this patch and release it.

> 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.9
>
>         Attachments: ZOOKEEPER-2614.branch-3.4.00.patch
>
>
> ZOOKEEPER-1576 handles UnknownHostException and it good to have this chan=
ge for 3.4 branch as well. Porting the changes to 3.4 after resolving the c=
onflicts


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