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/01 01:39:25 UTC
[jira] [Updated] (ZOOKEEPER-1950) configBackwardCompatibilityMode
breaks compatibility
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hongchao Deng updated ZOOKEEPER-1950:
-------------------------------------
Description:
The current implementation divide information of servers of legacy config into two separate dynamic config files. There is a problem.
When we set "clientPort" variable in config file, it gets automatically erased and later on there is no information about "clientPort" in either the old or new (.dynamic) config file.
It becomes a serious problem when users of *3.4* jump to *3.5* directly without changing their config: when a server crashes and restarts, there is no client port serving.
was:
The current implementation divide information of servers of legacy config into two separate dynamic config files. There is a problem.
When we set "clientPort" variable in config file, it gets automatically erased and later on there is no information about "clientPort" in either the old or new (.dynamic) config file.
It becomes a serious problem when users of *3.4* jump to *3.5* directly without changing their config. When a server crashes and restarts, there is no client port serving.
> configBackwardCompatibilityMode breaks compatibility
> ----------------------------------------------------
>
> Key: ZOOKEEPER-1950
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1950
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.5.0
> Reporter: Hongchao Deng
> Fix For: 3.5.0
>
>
> The current implementation divide information of servers of legacy config into two separate dynamic config files. There is a problem.
> When we set "clientPort" variable in config file, it gets automatically erased and later on there is no information about "clientPort" in either the old or new (.dynamic) config file.
> It becomes a serious problem when users of *3.4* jump to *3.5* directly without changing their config: when a server crashes and restarts, there is no client port serving.
--
This message was sent by Atlassian JIRA
(v6.2#6252)