[
https://issues.apache.org/jira/browse/ZOOKEEPER-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426219#comment-13426219
]
Jacob Mandelson commented on ZOOKEEPER-1502:
--------------------------------------------
On systems which use lockfiles, it's common to lockf the lockfile, so that an
orphaned lockfile can be easily identified by being lockf-able. Though this
can break on remote filesystems, it's really robust on local disk.
> Prevent multiple zookeeper servers from using the same data directory
> ---------------------------------------------------------------------
>
> Key: ZOOKEEPER-1502
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1502
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.4.3
> Reporter: Will Johnson
>
> We recently ran into an issue where two zookeepers servers which were a part
> of two separate quorums were configured to use the same data directory.
> Interestingly, the zookeeper servers did not seem to complain and both seemed
> to work fine until one of them was restarted. Once that happened all sort of
> chaos ensued. I understand that this is a misconfiguration should zookeeper
> complain about this or do users need to protect themselves in some external
> fashion? Is a simple file lock enough or are there other things I should
> take into consideration if it’s up to me to handle?
--
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
