[
https://issues.apache.org/jira/browse/ZOOKEEPER-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942213#comment-13942213
]
Patrick Hunt commented on ZOOKEEPER-1502:
-----------------------------------------
I mentioned this before
bq. Honestly it seems to me that this will raise more issues than it will
address. In particular I've never heard of anyone experiencing this issue
before. Failing to remove the lock file, and then not being able to start the
server, seems like it will be much more common.
and I'll just highlight it again to be sure everyone saw it. ;-)
Are we sure that this is something we really need? vs the many other issues
that might be worked on.
> 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)
