[
https://issues.apache.org/jira/browse/ZOOKEEPER-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14015061#comment-14015061
]
Alexander Shraer commented on ZOOKEEPER-1659:
---------------------------------------------
Thanks Rakesh! For the second question I meant this:
for remote bean:
CommonNames.DOMAIN + ":name0=ReplicatedServer_id" + nextIndex +
",name1=replica." + changingIndex;
for local bean: CommonNames.DOMAIN + ":name0=ReplicatedServer_id" +
leavingIndex + ",name1=replica." + leavingIndex;
the text here: https://zookeeper.apache.org/doc/r3.3.2/zookeeperJMX.html
indicates that the indices for replica.x and ReplicatedServer_id.x are the same
(myid of the server). Can you explain why in the case of remote bean the
indices are different ? should the documentation change ?
also, did you have a chance to try it with a jmx console ?
> 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, ZOOKEEPER-1659.patch,
> ZOOKEEPER-1659.patch, ZOOKEEPER-1659.patch, 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)
