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-2989) IPv6 literal address causes problems for Quorum members
Date Tue, 13 Mar 2018 19:49:00 GMT

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

ASF GitHub Bot commented on ZOOKEEPER-2989:

GitHub user troodes opened a pull request:


    ZOOKEEPER-2989: IPv6 literal address causes problems for Quorum members

    Handle tokenizing of "address:port" when address is an IPv6 literal address.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/troodes/zookeeper ZOOKEEPER-2989

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #489
commit 9e31f3448b6d5a950ea70ae715f26a8a0ca456d0
Author: Rick Trudeau <rick.trudeau@...>
Date:   2018-03-13T19:41:43Z

    ZOOKEEPER-2989: IPv6 literal address causes problems for Quorum members


> IPv6 literal address causes problems for Quorum members
> -------------------------------------------------------
>                 Key: ZOOKEEPER-2989
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2989
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: quorum
>    Affects Versions: 3.5.3
>            Reporter: Rick Trudeau
>            Priority: Major
> We're using ZK 3.5.3-beta.
> When using literal IPv6 addresses in the zoo.cfg.dynamic file, ZK fails to come up with the
connection to the peer ZKs keeps getting reset.
> zookeeper.log indicates a badly formed address is the cause.
> {noformat}
> <2018.03.01 15:14:30 163 -0500><E><sdn3></2001:db8:0:0:0:0:0:4:3888><org.apache.zookeeper.server.quorum.QuorumCnxManager>
Badly formed address: 2001:db8:0:0:0:0:0:2:3888{noformat}
> Our zoo.cfg.dynamic uses literal IPv6 addresses which according to ZOOKEEPER-1460 is
> {noformat}
> server.1=[2001:db8::2]:2888:3888;2181
> server.2=[2001:db8::3]:2888:3888;2181
> server.3=[2001:db8::4]:2888:3888;2181{noformat}
> Digging into QuorumCnxManager.java, InitialMessage.parse attemps to seperate the host
portion from the port portion using ":" as a delimeter, which is a problem for IPv6 IPs.  And
there's this comment:
> {code:java}
> // FIXME: IPv6 is not supported. Using something like Guava's HostAndPort
> // parser would be good.{code}
> So it looks like peers address:port is failing to be parsed if they are specified as
literal IPv6 addresses.  To confirm a workaround, I replaced my zoo.cfg.dynamic with hostnames
instead, and everything worked as expected.

This message was sent by Atlassian JIRA

View raw message