[
https://issues.apache.org/jira/browse/ZOOKEEPER-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14078596#comment-14078596
]
Alexander Shraer commented on ZOOKEEPER-1993:
---------------------------------------------
I see. Then perhaps you should create just one patch for ZK-1995, I don't
expect it to be big and you won't have to solve issue #2 just to remove the
solution a day later.
what about moving all changes related to standalone mode to a different Jira ?
like ZOOKEEPER-1997 which seems to be related to this issue ?
> It doesn't work
can you please give me an example of a config file where the check doesn't work
?
> Keep the client port upon parsing config
> ----------------------------------------
>
> Key: ZOOKEEPER-1993
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1993
> Project: ZooKeeper
> Issue Type: Sub-task
> Affects Versions: 3.5.0
> Reporter: Hongchao Deng
> Assignee: Hongchao Deng
> Priority: Blocker
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1993.patch, ZOOKEEPER-1993.patch,
> ZOOKEEPER-1993.patch
>
>
> 1. Current implementation ignored and removed "clientPort" on parsing. For
> the sake of backward compatibility, "clientPort" should be kept and used upon
> parsing config on fresh boot.
> 2. When getting clientPort from both the old config and dynamic file, the one
> in dynamic file is of higher priority.
> 3. When "dynamicConfigFile" is set in zoo.cfg and not empty, standalone mode
> will be disabled.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
