You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@zookeeper.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/02/13 17:30:00 UTC

[jira] [Updated] (ZOOKEEPER-3726) invalid ipv6 address comparison

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated ZOOKEEPER-3726:
--------------------------------------
    Labels: pull-request-available  (was: )

> invalid ipv6 address comparison
> -------------------------------
>
>                 Key: ZOOKEEPER-3726
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3726
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: c client
>    Affects Versions: 3.5.6
>            Reporter: Vladislav Tyulbashev
>            Priority: Major
>              Labels: pull-request-available
>
> Zookeeper C Client periodically resolves server names since https://issues.apache.org/jira/browse/ZOOKEEPER-1355
> After dns resolution ip addresses are checked against previous set of addresses. However, currently only several bytes are checked (it is assumed, that all addresses are ipv4 length bytes).
> Case:
> 1) zookeeper server operates only by ipv6
> 2) client connects to it by some hostname (zookeeper-1.news.yandex.ru, for example)
> 3) container with zookeeper server dies, new container is up, and zookeeper-1.news.yandex.ru now points to new address
> 4) several bits in ipv6 address are changed
> 5) zookeeper client ignores changes in address, because of incorrect strcmp size and first bytes were equal
> 6) zookeeper client now can't reconnect to zookeeper without manual intervention, because it tries old address
> pull request will be available shortly



--
This message was sent by Atlassian Jira
(v8.3.4#803005)