[
https://issues.apache.org/jira/browse/ZOOKEEPER-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flavio Paiva Junqueira updated ZOOKEEPER-151:
---------------------------------------------
Status: Open (was: Patch Available)
The current patch updates the documentation to explain how to configure a set
of ZooKeeper servers with the default leader election. This description
eliminates the old way of configuring that works with the original leader
election algorithm, though. Although the new way of configuring should also
work with the original leader election, it would be misleading to configure
another port and not use it.
Since we have currently two implementations (there are two more, but we've been
focusing on two), and they require different ways of configuring the servers, I
wonder if we should support both. Also, if we have different ways of
configuring, then to have both ways enabled, we would need to have both
"electionAlg" and server specs to determine if the configuration is correct,
thus creating a dependency between parameters. It is probably best to create
another jira to discuss the configuration issue, and leave this one for
documentation.
For now, I'm canceling this patch, and once we decide upon server
configuration, I can come back to this issue and update the patch.
> Document change to server configuration
> ---------------------------------------
>
> Key: ZOOKEEPER-151
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-151
> Project: Zookeeper
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Flavio Paiva Junqueira
> Assignee: Flavio Paiva Junqueira
> Fix For: 3.0.0
>
> Attachments: ZOOKEEPER-151.patch
>
>
> The patch of jira 127 changed the format of server configuration files, but
> it didn't change the documentation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
