You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Rakesh R (JIRA)" <ji...@apache.org> on 2014/03/20 10:31:44 UTC

[jira] [Commented] (ZOOKEEPER-1502) Prevent multiple zookeeper servers from using the same data directory

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941549#comment-13941549 ] 

Rakesh R commented on ZOOKEEPER-1502:
-------------------------------------

Hi All, I've tried an approach using the "java.nio.channels.FileLock". Please review the proposed patch. Thanks.

> 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)