You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Hongchao Deng (JIRA)" <ji...@apache.org> on 2014/07/28 04:06:38 UTC

[jira] [Created] (ZOOKEEPER-1992) backward compatibility of zoo.cfg

Hongchao Deng created ZOOKEEPER-1992:
----------------------------------------

             Summary: backward compatibility of zoo.cfg
                 Key: ZOOKEEPER-1992
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1992
             Project: ZooKeeper
          Issue Type: Bug
    Affects Versions: 3.5.0
            Reporter: Hongchao Deng
            Assignee: Hongchao Deng
            Priority: Blocker
             Fix For: 3.5.0


This issue supersedes our discussion in ZOOKEEPER-1989.

To summarize, ZK users can seamlessly upgrade 3.4 to 3.5. But two things will happen:
1. the server list will be separated out as a dynamic file (the original should be backup automatically).
2. Client port is mandatory on reconfig. So when reconfig the server itself (its id), the client port in config file will be removed and replaced by the one in reconfig (written in dynamic file).



--
This message was sent by Atlassian JIRA
(v6.2#6252)