[
https://issues.apache.org/jira/browse/ZOOKEEPER-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097684#comment-14097684
]
Hongchao Deng commented on ZOOKEEPER-2006:
------------------------------------------
[~shralex]
Okay. Adding a "standaloneEnabled=false" solve all the problems.
My concern is about two scenarios:
1. I set only one server in dynamic config.
dynamic file looks like
{code}
server.X=...participant; 2181
{code}
I wonder if it makes more sense to assume it is equal to
"standaloneEnabled=false" if "dynamicConfigFile" is set?
2. same as above. If it is not "standaloneEnabled=false", then the user has
made another mistake that client port is added only in dynamic file.
What do you think to deal with this?
> 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
>
> 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)
