[
https://issues.apache.org/jira/browse/ZOOKEEPER-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14099488#comment-14099488
]
Hongchao Deng commented on ZOOKEEPER-2006:
------------------------------------------
It looks like there is quite a few test failures.
The change I made in QuorumTestBase is that previously a MainThread will write
"clientPort" both to static config (zoo.cfg) and dynamic file. Something looks
like this, and it's duplicated.
{code}
clientPort=2181
...
server.1=localhost:X:X:participant;2181
{code}
After the change, if a user had written a "dynamicConfigFile" on bootup, it
won't have "clientPort" in static config. That's EXPECTED behavior.
I will try to figure out what is hidden in those failures. At the mean time,
anyone who has ideas please share.
> Standalone mode won't take client port from dynamic config file
> ---------------------------------------------------------------
>
> Key: ZOOKEEPER-2006
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2006
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.5.0
> Reporter: Hongchao Deng
> Assignee: Hongchao Deng
> Attachments: ZOOKEEPER-2006.patch, draft
>
>
> Currently, when a server only specify client port only in dynamic file, on
> standalone mode it will be ignored and no client port will be setup.
> It confuses the use of dynamic file and we should come up with something to
> handle this. One solution would be dynamic file doesn't allow standalone mode.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
