[
https://issues.apache.org/jira/browse/ZOOKEEPER-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949638#comment-13949638
]
Alexander Shraer commented on ZOOKEEPER-1659:
---------------------------------------------
Hi Rakesh,
To tell you the truth I've never used JMX, and not familiar with ZooKeeper
support for this, so [~phunt] may have a better idea of what we need here. My
guess is that we'd want to at least see the latest committed dynamic config,
even better would be to know what it is at different servers so that we know if
some server has a stale config. With regard to in-progress reconfigs, I'm not
sure how this would work since they only take a few ms at most (as any other
op). State transfer happens before the reconfig is invoked. Perhaps reconfig
proposal and commit times can be recorded, but this seems lower priority.
It would be good to monitor the set of servers connected/synced to the leader
and their roles (some of them will be paticipants/observers in the current
config and others may be non-voting followers, that don't belong to the current
config). This way an operator can know that server A is already in-sync with
the leader and he can invoke reconfig to add A.
In general we probably want to add some minimal support first so that its no
longer a blocker for 3.5.0, and then potentially add more info if needed.
Alex
> 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
> Priority: Blocker
> Fix For: 3.5.0
>
>
> 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)
