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 74C9310626 for ; Mon, 10 Nov 2014 22:14:26 +0000 (UTC) Received: (qmail 57695 invoked by uid 500); 10 Nov 2014 22:14:25 -0000 Delivered-To: apmail-zookeeper-user-archive@zookeeper.apache.org Received: (qmail 57651 invoked by uid 500); 10 Nov 2014 22:14:25 -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 57639 invoked by uid 99); 10 Nov 2014 22:14:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Nov 2014 22:14:25 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of shralex@gmail.com designates 209.85.213.41 as permitted sender) Received: from [209.85.213.41] (HELO mail-yh0-f41.google.com) (209.85.213.41) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Nov 2014 22:13:59 +0000 Received: by mail-yh0-f41.google.com with SMTP id i57so3736144yha.28 for ; Mon, 10 Nov 2014 14:13:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=awYFH4P2bfvulTW7sfJvehWdykLRSYrPcA7okUcSJNs=; b=umjSPpi1vDGx2AQyGBC+Rn9+jJg4wXGIWIlKQcJfAadp+PrSAnrtgwHcj8bpeCxmzV vQ7o2MzOAQhzJvCBR6iRo5WWlP+nLyLyvr/wLHAJE8RUjSHQvzEm6M+XfBhPeTUJPx0d se2HzKoBkeUuTklqxHGa/aGol62BjxzkNlzjRLDuej62J7TmuiiVVzia4X0r9IaYpNi6 0iuKKnZ/OixqBAO6du/SlPlJ2IiqWENlyxjToA8kan80qCZok6ti7l8eBLF898WsB/cC ERtg6itj51Pf0NxZtjmJZO0k4ur8zhHNyC5CBr/oMEhvxuHxvQSx0Xl3wlj9tqAhBLty f4pQ== X-Received: by 10.52.5.196 with SMTP id u4mr2020126vdu.66.1415657593576; Mon, 10 Nov 2014 14:13:13 -0800 (PST) MIME-Version: 1.0 Received: by 10.31.163.2 with HTTP; Mon, 10 Nov 2014 14:12:53 -0800 (PST) In-Reply-To: References: From: Alexander Shraer Date: Mon, 10 Nov 2014 14:12:53 -0800 Message-ID: Subject: Re: NewConfigNoQuorum? To: "user@zookeeper.apache.org" Content-Type: multipart/alternative; boundary=20cf303343b5fd238e0507887763 X-Virus-Checked: Checked by ClamAV on apache.org --20cf303343b5fd238e0507887763 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable This happens if you're trying to reconfigure to a new configuration S' but there is no quorum of S' connected and synced with the current leader. This could be either transient or more serious, depends... For example it could be the case that you are trying to add a few servers and there is a lot of state so syncing isn't complete yet and you just need to retry later. On the other hand it could be that S' includes servers that have crashed or don't exist, so retrying won't help. On Mon, Nov 10, 2014 at 8:54 AM, Ivan Kelly wrote: > Isn't this a transient error that occurs while the cluster is > reconfiguring? Seems to me that a retry would be correct. > > -Ivan > > On 10 November 2014 16:56, Jordan Zimmerman > wrote: > > In Alexander=E2=80=99s ZK meetup talk, he mentioned a new exception: > NewConfigNoQuorum. How should Curator handle this? Should the reconfig > operation just be retried when this is thrown or does it imply a deeper > problem? > > > > -Jordan > > > > > --20cf303343b5fd238e0507887763--