[
https://issues.apache.org/jira/browse/ZOOKEEPER-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14012072#comment-14012072
]
Rakesh R commented on ZOOKEEPER-1659:
-------------------------------------
Sometime back myself and Alex had a private discussion to understand more on
the reconfig behaviours. Thanks [~shralex]. Here one thing come across is, even
after removal of quorum peer from the configuration, the server will be running
fine and old clients as well as new clients will work happily. Also, the
QuorumPeer parameters are likely not affected either. Considering these cases,
IMHO LocalPeerBean(self) can be accessible to the external users as long as the
server is alive, what others opinion?.
Following are the attributes of LocalPeerBean:
- State
- QuorumAddress
- ElectionAddress
- LearnerType
- ClientAddress
- ElectionType
- TickTime
- MaxClientCnxnsPerHost
- MinSessionTimeout
- MaxSessionTimeout
- InitLimit
- Tick
- SyncLimit
- Name
- StartTime
Now as part of this patch proposal we will be adding the following attributes
too.
- QuorumSystemInfo
- ConfigVersion
> 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
>
>
> 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)
