Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-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 5DF2FDD29 for ; Wed, 1 Aug 2012 18:41:47 +0000 (UTC) Received: (qmail 3056 invoked by uid 500); 1 Aug 2012 18:41:44 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 3011 invoked by uid 500); 1 Aug 2012 18:41:44 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 3002 invoked by uid 99); 1 Aug 2012 18:41:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Aug 2012 18:41:44 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mohitanchlia@gmail.com designates 209.85.213.169 as permitted sender) Received: from [209.85.213.169] (HELO mail-yx0-f169.google.com) (209.85.213.169) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Aug 2012 18:41:38 +0000 Received: by yenr5 with SMTP id r5so9084452yen.14 for ; Wed, 01 Aug 2012 11:41:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=waQpLZC16g3KeuqbvabHA06C+UUVcPZwdV2HUD0AybQ=; b=CJJvzqfLWD0P3bDKHs+WG1vGjrW2dEt9cowDF5B3Jt+x3D6Ce4b+Nx26d4Ij+W991+ AInHD4blqQYm/Lr7y3dhKiYVpQcbGjqOT5dPHhOpVIxJIflPD4y3g1VFIMr4nzkvFbnE tlo1QPvbWqrOdCKWTOrZ5C6PMYM6NCBxYtx84f+MNoHDDEavJCfVo57qJmcJahvDso3L 4QJNFnDWdOildnvUe5xGD2IxAW86+FX+y0ddrk1WuSgOivE/1SM3lmC+zoSRVBM3C3te 4BjhVwCqMkV07eOcAJnZ/Nlv9v0oAIDFQ32FClwCGLcvbr93eET3QRGDNf5PrXrONg+7 hVAQ== MIME-Version: 1.0 Received: by 10.50.203.41 with SMTP id kn9mr6330324igc.72.1343846477544; Wed, 01 Aug 2012 11:41:17 -0700 (PDT) Received: by 10.64.65.1 with HTTP; Wed, 1 Aug 2012 11:41:17 -0700 (PDT) Date: Wed, 1 Aug 2012 11:41:17 -0700 Message-ID: Subject: Region server failure question From: Mohit Anchlia To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=14dae934119fed3ed204c638a39a --14dae934119fed3ed204c638a39a Content-Type: text/plain; charset=ISO-8859-1 I was reading blog http://www.cloudera.com/blog/2012/07/hbase-log-splitting/ and it looks like if region servers fails then all the regions on that region servers are unavailable until a regions are assigned to a different region server. Does it mean all the key ranges for the failed region server is unavailable for reads and writes until regions are available on some other region server? If so then how to deal with failures while real time data might be flowing into HBase. --14dae934119fed3ed204c638a39a--