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 B982F10E7D for ; Thu, 19 Feb 2015 14:56:28 +0000 (UTC) Received: (qmail 99346 invoked by uid 500); 19 Feb 2015 14:56:24 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 99280 invoked by uid 500); 19 Feb 2015 14:56:23 -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 99268 invoked by uid 99); 19 Feb 2015 14:56:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Feb 2015 14:56:23 +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 yuzhihong@gmail.com designates 209.85.160.181 as permitted sender) Received: from [209.85.160.181] (HELO mail-yk0-f181.google.com) (209.85.160.181) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Feb 2015 14:55:57 +0000 Received: by mail-yk0-f181.google.com with SMTP id 200so4201690ykr.12 for ; Thu, 19 Feb 2015 06:55:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=mG7n9QzmnZ7nwZC84myVTS+Ipu2aP4NRxRuLVeUuDlU=; b=DoLz4bPdsVozHatpzjWEwE1vCkQTgF84y2W+v0Qb3n8lMKOmvoN6rbH0PzcxHT0dCI Y9iNbjWN/gQzf34BvWTInLNl51UKC6VL5FUWkRtfswgH9qZwYulpMduOOOrjb+lpYIu/ Q2mmH0l/UeX7Z2fkOndzdNgOUCzOzuFbOC8AJ3N7pHwhkYemV5vv5bnEaxsKuxesWF7U fRqQ8F6rtKHjQ7+6y4/oR9SXV6BxLGvMZWC75hdmVMWRo4r2G4l79o/SKnzUD3Jb0XkQ opt6MltZHXGvp/1cCQ84gDiBizcJkblqhsnyu2eqE+2HJsJ2cXIOKfkS1J6JwvZgLEZp 1t1g== MIME-Version: 1.0 X-Received: by 10.236.110.133 with SMTP id u5mr3148021yhg.150.1424357755810; Thu, 19 Feb 2015 06:55:55 -0800 (PST) Received: by 10.170.111.72 with HTTP; Thu, 19 Feb 2015 06:55:55 -0800 (PST) In-Reply-To: References: Date: Thu, 19 Feb 2015 06:55:55 -0800 Message-ID: Subject: Re: HBase mttr From: Ted Yu To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a1133d5661177fe050f722212 X-Virus-Checked: Checked by ClamAV on apache.org --001a1133d5661177fe050f722212 Content-Type: text/plain; charset=UTF-8 Have you read '9.3.4. Better Mean Time to Recover (MTTR)' under http://hbase.apache.org/book.html#important_configurations ? For #2, can you take a look at https://issues.apache.org/jira/browse/HBASE-10070 ? Cheers On Thu, Feb 19, 2015 at 12:46 AM, Serega Sheypak wrote: > Hi, we are running HBase on super-low-cost HW :) > Sometimes random node goes down. And HBase needs a time to move regions > from failed RS. > > What are the practices to: > 1. minimize MTTR? > 2. is there any possibility to gracefully handle situation when region is > not accessible for r/w? > I can just drop the data, but I can't wait seconds or minutes for response. > I would like to break request after 100ms and return empty result. > --001a1133d5661177fe050f722212--