[ https://issues.apache.org/jira/browse/ZOOKEEPER-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796413#comment-13796413 ]
Alexander Shraer commented on ZOOKEEPER-1783: --------------------------------------------- thanks for reviewing!! > Distinguish initial configuration from first established configuration > ---------------------------------------------------------------------- > > Key: ZOOKEEPER-1783 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1783 > Project: ZooKeeper > Issue Type: Bug > Components: quorum, server > Affects Versions: 3.5.0 > Reporter: Alexander Shraer > Assignee: Alexander Shraer > Fix For: 3.5.0 > > Attachments: ZOOKEEPER-1783.patch, ZOOKEEPER-1783-ver1.patch, > ZOOKEEPER-1783-ver2.patch, ZOOKEEPER-1783-ver3.patch, > ZOOKEEPER-1783-ver4.patch, ZOOKEEPER-1783-ver5.patch, > ZOOKEEPER-1783-ver6.patch, ZOOKEEPER-1783-ver7.patch, > ZOOKEEPER-1783-ver8.patch > > > We need a way to distinguish an initial config of a server and an initial > config of a running ensemble (before any reconfigs happen). Currently both > have version 0. > The version of a config increases with each reconfiguration, so the problem > is just with the initial config. -- This message was sent by Atlassian JIRA (v6.1#6144)