Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id BB33F200B3B for ; Mon, 11 Jul 2016 14:30:52 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B9C69160A78; Mon, 11 Jul 2016 12:30:52 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 341B3160A62 for ; Mon, 11 Jul 2016 14:30:52 +0200 (CEST) Received: (qmail 63684 invoked by uid 500); 11 Jul 2016 12:30:51 -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 63668 invoked by uid 99); 11 Jul 2016 12:30:51 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Jul 2016 12:30:51 +0000 Received: from mail-it0-f54.google.com (mail-it0-f54.google.com [209.85.214.54]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id D9DBE1A0046 for ; Mon, 11 Jul 2016 12:30:50 +0000 (UTC) Received: by mail-it0-f54.google.com with SMTP id f6so53667428ith.0 for ; Mon, 11 Jul 2016 05:30:50 -0700 (PDT) X-Gm-Message-State: ALyK8tIq+iqeI9t2wTNHOGyPrA5V/FYuIFl73z0ZxZmqHoGF8XyJSXF5zO00tw5Y0qa7L4uH7tsA+1Sj2aSWKw== MIME-Version: 1.0 X-Received: by 10.36.62.133 with SMTP id s127mr4639088its.98.1468240250125; Mon, 11 Jul 2016 05:30:50 -0700 (PDT) Received: by 10.64.164.6 with HTTP; Mon, 11 Jul 2016 05:30:50 -0700 (PDT) Received: by 10.64.164.6 with HTTP; Mon, 11 Jul 2016 05:30:50 -0700 (PDT) In-Reply-To: <050c01d1db69$19b7cce0$4d2766a0$@gmail.com> References: <050c01d1db69$19b7cce0$4d2766a0$@gmail.com> Date: Mon, 11 Jul 2016 08:30:50 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Does Zoo still provides reads when 1 node fails out of 2 nodes with quorum set to 2? From: Camille Fournier To: user@zookeeper.apache.org Content-Type: multipart/alternative; boundary=001a113fe08c8dcccb05375b52fc archived-at: Mon, 11 Jul 2016 12:30:52 -0000 --001a113fe08c8dcccb05375b52fc Content-Type: text/plain; charset=UTF-8 We support a read only mode configuration that will allow clients who wish to see disconnected nodes in read only mode. We do not support defaulting clusters into this configuration based on their configured size, because the edge cases there would be a headache and we don't recommend running two node clusters in general. C On Jul 11, 2016 7:41 AM, "Vladimir Picka" wrote: > Hello, > > See subject, .or both nodes, split but possibly still accessible, becomes > unavailable for reading? > > I think in this special scenario of 2 nodes with quorum 2 reading could be > still provided when one fails because none node has quorum hence none can > write and change the last agreed state. If not, can you explain why? > > > > Many thanks, > > Petr > > --001a113fe08c8dcccb05375b52fc--