[
https://issues.apache.org/jira/browse/ZOOKEEPER-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944466#comment-13944466
]
Ted Dunning commented on ZOOKEEPER-1502:
----------------------------------------
File locking is notoriously unreliable. There is a history of it not even
working correctly on local physical volumes and there are many examples of it
not working correctly on SAN and NAS devices.
Depending on it, is not a great idea. At the very least, you should make sure
that the code works if flock is not available.
> 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
> Assignee: Rakesh R
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1502.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)
