zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Dunning (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-1502) Prevent multiple zookeeper servers from using the same data directory
Date Wed, 01 Aug 2012 00:41:34 GMT

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

Ted Dunning commented on ZOOKEEPER-1502:
----------------------------------------

Another, more robust option, is to put the PID of the ZK process into the lock file.  If that
process doesn't exist or isn't a ZK process, then the lock is an orphan and can be removed.
 Touching the file every minute or so also makes identification of an orphan very easy.

Other systems that use a similar approach include mySQL, Solr and mongodb.  
                
> 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

       

Mime
View raw message