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 EE9391026D for ; Wed, 19 Mar 2014 05:18:08 +0000 (UTC) Received: (qmail 99440 invoked by uid 500); 19 Mar 2014 05:18:05 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 99129 invoked by uid 500); 19 Mar 2014 05:18:04 -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 99121 invoked by uid 99); 19 Mar 2014 05:18:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Mar 2014 05:18:03 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of upendra1024@gmail.com designates 209.85.215.43 as permitted sender) Received: from [209.85.215.43] (HELO mail-la0-f43.google.com) (209.85.215.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Mar 2014 05:17:57 +0000 Received: by mail-la0-f43.google.com with SMTP id e16so5489815lan.2 for ; Tue, 18 Mar 2014 22:17:36 -0700 (PDT) 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=C7o+2j0nTSuU0a0m6NQEFsR36fV0hdms8xMNlIdLn/s=; b=xM3AoVvR/cWl/sfU2nK2rkNdpGwvPpWXeby3FxQfRfGfveCdzKPM+SfkmTDgBeEB4f hzp+nkYyq/M7yLBT9zrZyuXRro07taLJAQy8Sv2i7Y7cjxqXDX97rBNzJYj8pmQz/vdE hVq/JR9IMWHEV2q7Y/TCs+l24c7D7mXDGGBtZta6rjFXC5m54Rxmfgqj2T8UT4Rlgmjd bA2uhm5hP8m69+AuI3YGR8VYYg9Hy6tS33va8FyOR8Aoy5OQH6nltINl1iR9JPKUfLB3 L6c00gAvAt5NeAqr+SMMucz2gfxhytVCLyW04+vZ849CV+4sBGwmr86OxbUYw840eFiM rNGA== MIME-Version: 1.0 X-Received: by 10.153.7.69 with SMTP id da5mr202795lad.38.1395206255963; Tue, 18 Mar 2014 22:17:35 -0700 (PDT) Received: by 10.112.140.101 with HTTP; Tue, 18 Mar 2014 22:17:35 -0700 (PDT) In-Reply-To: <40673396-C987-40FE-B2FE-16433E2E2FF3@gmail.com> References: <40673396-C987-40FE-B2FE-16433E2E2FF3@gmail.com> Date: Wed, 19 Mar 2014 10:47:35 +0530 Message-ID: Subject: Re: How much time HBase will take if one Region Server down. From: Upendra Yadav To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=001a1134563046708304f4eec5ec X-Virus-Checked: Checked by ClamAV on apache.org --001a1134563046708304f4eec5ec Content-Type: text/plain; charset=ISO-8859-1 yes demai... i understood... On Wed, Mar 19, 2014 at 1:00 AM, Demai Ni wrote: > You are welcome. Btw, I mean Hbase 96+and Hadoop 2 in my previous reply. > > Demai on the run > > On Mar 18, 2014, at 12:07 PM, Upendra Yadav wrote: > > > Thanks Demai... > > i will go through your link.... > > > > > > On Tue, Mar 18, 2014 at 11:29 PM, Demai Ni wrote: > > > >> a good article to start with: > >> > >> > http://hortonworks.com/blog/introduction-to-hbase-mean-time-to-recover-mttr/ > >> > >> I would say 15~20 min for 94 or earlier; it can be reduced to a couple > min > >> with HBase 96+ and Hadoop . > >> > >> Demai > >> > >> > >> On Tue, Mar 18, 2014 at 10:55 AM, Upendra Yadav >>> wrote: > >> > >>> How much time HBase will take if one Region Server down and try to read > >>> Region that belong to this down Region Server. > >>> > >>> Means Is there service down for those all region that belongs to dead > RS? > >>> > >>> How much time HMaster will take to assign those region to live RS? What > >> is > >>> the dependencies that may increase region assignment in such situation. > >>> > >>> Thanks.... > >> > --001a1134563046708304f4eec5ec--