Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 65F3895F3 for ; Sat, 12 May 2012 21:51:10 +0000 (UTC) Received: (qmail 81705 invoked by uid 500); 12 May 2012 21:51:09 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 81664 invoked by uid 500); 12 May 2012 21:51:09 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 81654 invoked by uid 99); 12 May 2012 21:51:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 May 2012 21:51:09 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of saint.ack@gmail.com designates 209.85.212.41 as permitted sender) Received: from [209.85.212.41] (HELO mail-vb0-f41.google.com) (209.85.212.41) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 12 May 2012 21:51:02 +0000 Received: by vbbey12 with SMTP id ey12so6032423vbb.14 for ; Sat, 12 May 2012 14:50:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=cgMV2LI3fKhol1zQPXk0vnNiVvzLj1qIrHiBmlZ0pTQ=; b=A7Jcl22Dg4rlo7jXROMH3QCweaFFpqe6CLF3oWdWdQPLHWLqyv9tF/4UQMUQ4iOKX7 3sbe4MFNX52rkTExRSQuhxatihA7ZJFbMpBAYUcdJtV7bSAf6YPogvFhRH1sPOLamoes NlDZx+gx65KXIPgRcnaCAVbyDbSuaorsoZLF3eXk+D8nKmMvxrs+1rY6k0gBoGRQFH7h G3muYRvGSzVK0dT1n5Q08lLM3QCjwCidkBt0aGlReoMJZjU0eVwC2339duVeGxHRkJ92 +EehAIF/T4BPPUYmCVuTB1MHpDA9hkXk6RlGqLqzjWkajgQBmrEemf++sv73liBmC3mk I/zQ== MIME-Version: 1.0 Received: by 10.220.141.15 with SMTP id k15mr1845132vcu.30.1336859441333; Sat, 12 May 2012 14:50:41 -0700 (PDT) Sender: saint.ack@gmail.com Received: by 10.220.5.85 with HTTP; Sat, 12 May 2012 14:50:41 -0700 (PDT) In-Reply-To: References: <1335914771.79923.YahooMailNeo@web121706.mail.ne1.yahoo.com> Date: Sat, 12 May 2012 14:50:41 -0700 X-Google-Sender-Auth: Kw8PUox_ync_hMYAv94LA4rgTEc Message-ID: Subject: Re: ANN: The third hbase 0.94.0 release candidate is available for download From: Stack To: dev@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Sat, May 12, 2012 at 10:14 AM, Mikael Sitruk w= rote: > Thanks for the clarifications St.Ack. > Still I have some questions in regards of 3 in scenario discussed - =A0wh= en a > region is offline it means that client operation are not possible on it > (even read)? Correct. > In case a second master is up (in an environment with multiple master), i > presume all this occurs unless the second master (slave) become the maste= r, > right? how long those it take for a "slave" master to become a master?? > It takes seconds roughly for new master to assume master role and to figure the state of the cluster. The processing of a failed server though can take seconds, minutes, or even hours at an extreme where the server was running with pathological configs. How long to process WALs is a function of the number of WAL files the server was carrying in need of replay and the number of servers available to participate in the distributed log splitting affair. Ask more questions Mikael, St.Ack