Return-Path: X-Original-To: apmail-zookeeper-user-archive@www.apache.org Delivered-To: apmail-zookeeper-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 164B2D100 for ; Thu, 5 Jul 2012 17:10:21 +0000 (UTC) Received: (qmail 56968 invoked by uid 500); 5 Jul 2012 17:10:20 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 56934 invoked by uid 500); 5 Jul 2012 17:10:20 -0000 Mailing-List: contact user-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@zookeeper.apache.org Delivered-To: mailing list user@zookeeper.apache.org Received: (qmail 56926 invoked by uid 99); 5 Jul 2012 17:10:20 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jul 2012 17:10:20 +0000 Received: from localhost (HELO mail-gg0-f170.google.com) (127.0.0.1) (smtp-auth username phunt, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jul 2012 17:10:20 +0000 Received: by ggnf2 with SMTP id f2so7014589ggn.15 for ; Thu, 05 Jul 2012 10:10:19 -0700 (PDT) Received: by 10.60.169.174 with SMTP id af14mr27377988oec.13.1341508219297; Thu, 05 Jul 2012 10:10:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.116.101 with HTTP; Thu, 5 Jul 2012 10:09:59 -0700 (PDT) In-Reply-To: References: <9694A6C3D68A4249BD9E1A875B6BA81E0AB367FD3B@bos0ex01.corp.attivio.com> From: Patrick Hunt Date: Thu, 5 Jul 2012 10:09:59 -0700 Message-ID: Subject: Re: multiple zookeepers - same data directory To: user@zookeeper.apache.org Content-Type: text/plain; charset=ISO-8859-1 Yes, please file a jira for this. Patrick On Thu, Jul 5, 2012 at 10:01 AM, Camille Fournier wrote: > There's nothing to prevent this as it stands, no, except user action. A > lock file might not be a bad idea. > > C > > On Thu, Jul 5, 2012 at 12:53 PM, Will Johnson wrote: > >> 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? >> >> I'm happy to file a jira for this as I didn't see any doc related to it >> but I wanted to see if I missed something first. >> >> >> - will >>