[
https://issues.apache.org/jira/browse/ZOOKEEPER-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097651#comment-14097651
]
Alexander Shraer commented on ZOOKEEPER-2006:
---------------------------------------------
In general I don't think improving standalone mode is worth it. The recent
introduction of the standaloneEnabled flag and the related support for running
the normal non-standalone stack with a single server ensemble makes standalone
mode unnecessary. One would probably pretty much always prefer to run with
standaloneEnabled = false in a distributed mode. So I expect standalone mode to
go away in the future.
> Pre-assumption: "standaloneEnabled" and "dynamicConfigFile" is mutually
> exclusive in config file.
I don't think this is true. standaloneEnabled may be true or false depending on
whether one wants to allow the cluster to shrink to a single server. at the
same time dynamicConfigfile can be specified.
> Backward-compatibility: A single line – "server.X=..." in static config file
> is still standalone mode.
Not sure about that. Standalone mode doesn't understand what a quorum or leader
port is, what an observer is, etc. So writing such a line is kindof strange in
standalone mode.
> 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)
