[
https://issues.apache.org/jira/browse/ZOOKEEPER-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956389#comment-13956389
]
Hudson commented on ZOOKEEPER-1701:
-----------------------------------
SUCCESS: Integrated in ZooKeeper-trunk #2276 (See
[https://builds.apache.org/job/ZooKeeper-trunk/2276/])
ZOOKEEPER-1701. When new and old config have the same version, no need to write
new config to disk or create new connections (Alexander Shraer via michim)
(michim:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1583509)
* /zookeeper/trunk/CHANGES.txt
*
/zookeeper/trunk/src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java
> When new and old config have the same version, no need to write new config to
> disk or create new connections
> ------------------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1701
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1701
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.5.0
> Reporter: Alexander Shraer
> Assignee: Alexander Shraer
> Priority: Minor
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1701.patch, ZOOKEEPER-1701.patch
>
>
> setLastSeenQuorumVerifier in QuorumPeer.java always writes the new config to
> disk and tries to make new connections to servers in new config. When the new
> config has the same version as the committed one (e.g., when the config
> received in a NEWLEADER message is already known to the follower), there's no
> need to write it to disk or to create new connections.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
