[
https://issues.apache.org/jira/browse/ZOOKEEPER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697220#action_12697220
]
Stu Hood commented on ZOOKEEPER-29:
-----------------------------------
Two comments:
----
This ticket seems to overlap with ZOOKEEPER-368 to some degree: wouldn't an
Observer simply be a server in the quorum that wouldn't get to vote on proposed
values?
----
{quote}
I find mixing this quorum representation with the current configuration a
little messy, especially because it is an optional feature and it does
correspond to a simple value loaded from a file. We need some logic to perform
quorum verification aside from values that we load from a separate
configuration file.
{quote}
It could probably correspond to a key loaded from a flat file, if the key was
hierarchial. It would require a bit of a config overhaul: rather than
{code}
server.1=ahost:2181:2888
{code}
.. you'd want
{code}
server.1.hostname=ahost
server.1.port=2181
server.1.otherport=2888
server.1.weight=3
{code}
...so then weight is optional, which defaults to an equal weight for all
servers.
> Flexible quorums
> ----------------
>
> Key: ZOOKEEPER-29
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-29
> Project: Zookeeper
> Issue Type: New Feature
> Components: server
> Reporter: Patrick Hunt
> Assignee: Flavio Paiva Junqueira
> Attachments: ZOOKEEPER-29.patch, ZOOKEEPER-29.patch,
> ZOOKEEPER-29.patch
>
>
> Moved from SourceForge to Apache.
> http://sourceforge.net/tracker/index.php?func=detail&aid=1938782&group_id=209147&atid=1008547
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
