[
https://issues.apache.org/jira/browse/ZOOKEEPER-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000458#comment-14000458
]
Alexander Shraer commented on ZOOKEEPER-1659:
---------------------------------------------
I'd like to go over this too - probably over the weekend. Sorry for the delay,
Rakesh!
> "I've one question, what will happen to the qp server which is leaving the
> quorum ?
> In the patch it will not remove the self mxbean, considering that admin will
> make it down and during that time the jmx
> beans will get automatically unregistered. Is that fine ?"
Intuitively it'd be good if all the places listing the configuration are kept
consistent. So I'd say that the server should remove itself from this list so
that the list in the config znode and in the JMX are consistent. Also -
removing a server may not lead to shutting it down - it may be an intermediate
step for changing its role (there are cases where this is necessary when
changing an observer to a follower - an observer can't vote so if its vote is
needed to establish the new config we may need to first remove it so that its a
non-voting follower).
> Add JMX support for dynamic reconfiguration
> -------------------------------------------
>
> Key: ZOOKEEPER-1659
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1659
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.5.0
> Reporter: Alexander Shraer
> Assignee: Rakesh R
> Priority: Blocker
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1659.patch
>
>
> We need to update JMX during reconfigurations. Currently, reconfiguration
> changes are not reflected in JConsole.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
