zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enrico Olivelli (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (ZOOKEEPER-3540) Client port unavailable after binding the same client port during reconfig
Date Tue, 10 Sep 2019 16:52:00 GMT

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

Enrico Olivelli resolved ZOOKEEPER-3540.
----------------------------------------
    Resolution: Fixed

> Client port unavailable after binding the same client port during reconfig
> --------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-3540
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3540
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.6.0
>            Reporter: Fangmin Lv
>            Assignee: Fangmin Lv
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.6.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> When dynamically replace a server with IPv4/IPv6 with the same port, the server will
complain about 'address already in use', and cause the client port not available anymore.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message