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

Posted to dev@zookeeper.apache.org by "Fangmin Lv (Jira)" <ji...@apache.org> on 2019/09/09 16:42:00 UTC

[jira] [Created] (ZOOKEEPER-3540) Client port unavailable after binding the same client port during reconfig

Fangmin Lv created ZOOKEEPER-3540:
-------------------------------------

             Summary: 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
             Fix For: 3.6.0


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)