[
https://issues.apache.org/jira/browse/ZOOKEEPER-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421153#comment-13421153
]
Alexander Shraer commented on ZOOKEEPER-107:
--------------------------------------------
Hi Flavio,
I haven't touched currentEpoch. But seems like this file shouldn't exist at
all. If I'm not mistaken it is created in QuorumPeer.writeLongToFile (a recent
addition that writes atomically) called from QuorumPeer.setCurrentEpoch and in
the comments there its says that the tmp file will exists only if the atomic
write failed. I'm not sure why this happens and actually I couldn't find the
corresponding error message in the hudson execution logs (maybe I wasn't
looking in the right place).
Alex
> Allow dynamic changes to server cluster membership
> --------------------------------------------------
>
> Key: ZOOKEEPER-107
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-107
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Reporter: Patrick Hunt
> Assignee: Alexander Shraer
> Fix For: 3.5.0
>
> Attachments: SimpleAddition.rtf, ZOOKEEPER-107-1-Mar.patch,
> ZOOKEEPER-107-20-July.patch, ZOOKEEPER-107-21-July.patch,
> ZOOKEEPER-107-22-Apr.patch, ZOOKEEPER-107-28-Feb.patch,
> ZOOKEEPER-107-28-Feb.patch, ZOOKEEPER-107-29-Feb.patch,
> zkreconfig-usenixatc-final.pdf, zoo_replicated1.cfg, zoo_replicated1.members,
> zookeeper-3.4.0.jar, zookeeper-dev-fatjar.jar,
> zookeeper-reconfig-sep11.patch, zookeeper-reconfig-sep12.patch
>
>
> Currently cluster membership is statically defined, adding/removing hosts
> to/from the server cluster dynamically needs to be supported.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
