[
https://issues.apache.org/jira/browse/ZOOKEEPER-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380380#comment-15380380
]
Alexander Shraer commented on ZOOKEEPER-2476:
---------------------------------------------
The recommended way to deal with this is to first remove the observer (reconfig
it out) which will turn it into a "non-voting follower", and then he can
technically vote (his votes will not be counted for the old config, but will be
counted during a reconfig you'll do next). Then reconfig add it as a
participant. So the conversion is possible using two reconfigs instead of one.
> Not possible to upgrade via reconfig a Participant+Observer cluster to a
> Participant+Participant cluster
> --------------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2476
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2476
> Project: ZooKeeper
> Issue Type: Bug
> Components: quorum, server
> Affects Versions: 3.5.1
> Reporter: Jordan Zimmerman
> Assignee: Alexander Shraer
> Priority: Critical
> Attachments: ZOOKEEPER-2476.patch
>
>
> Contrary to the documentation, it is not possible to upgrade via reconfig a
> Participant+Observer cluster to a Participant+Participant cluster.
> KeeperException.NewConfigNoQuorum is thrown instead.
> PrepRequestProcessor should recognize this special case and let it pass. Test
> will be enclosed shortly. I'll work on a fix as well, but I imagine that
> [~shralex] will want to look at it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
