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 93CAA10AF9 for ; Fri, 20 Sep 2013 23:15:09 +0000 (UTC) Received: (qmail 67183 invoked by uid 500); 20 Sep 2013 23:15:05 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 67112 invoked by uid 500); 20 Sep 2013 23:15:05 -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 67103 invoked by uid 99); 20 Sep 2013 23:15:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Sep 2013 23:15:03 +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 nidmgg@gmail.com designates 209.85.128.177 as permitted sender) Received: from [209.85.128.177] (HELO mail-ve0-f177.google.com) (209.85.128.177) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Sep 2013 23:14:57 +0000 Received: by mail-ve0-f177.google.com with SMTP id db12so855185veb.22 for ; Fri, 20 Sep 2013 16:14:36 -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=rbekAgkp+PX0JKt7qBAqtFM9nBeCdxdhhZWN1ad2Ypk=; b=EqUzB1Tpp/yc5xhwsXAlwflSCOkq9x/nRFkWP8THnMGU5jSueThxZFfBQRhtauq9Pb 9j7aWY7IGuOHGlGdTI8bpzroNWpGGy5Re8OH2Ckt5sDbzG5OensHU607raPNvgWgEbSC bIkZAN8NzOqUnxchM2T8oHYZCzjsBbmwytXCbk6g6fc2ev9x6HLPtgfe4nSnbXwOdTrw KhciHIWp1ltaBXqjuek4qdHeQNFMietyLrjTby+srXA3XnTsKG/0noekLStTsVbco1QX krsAzm96DN19cpy4AXDu/nyBZ9MAW2us5uEWai8VWhcS7BblE0tTxPN8cR6Lya4+lTOl 4l6A== MIME-Version: 1.0 X-Received: by 10.220.74.69 with SMTP id t5mr8730145vcj.18.1379718876120; Fri, 20 Sep 2013 16:14:36 -0700 (PDT) Received: by 10.221.28.136 with HTTP; Fri, 20 Sep 2013 16:14:36 -0700 (PDT) Date: Fri, 20 Sep 2013 16:14:36 -0700 Message-ID: Subject: hbase regionserver fail over -- how long it will take? From: Demai Ni To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=047d7b624cbe804e7b04e6d8d52f X-Virus-Checked: Checked by ClamAV on apache.org --047d7b624cbe804e7b04e6d8d52f Content-Type: text/plain; charset=ISO-8859-1 hi, folks, My understanding of hbase within cluster highavailability is to keep 3 copy of data(dfs.replication, default is 3). Whenever a region server fails(offlline), another regionserver, which contain another copy of the data, will pick up. Is my understanding correct? In that case, usually how long will take the failover to complete, so that the data will be available? Can I get a couple pointers? or on-line doc? many thanks Demai --047d7b624cbe804e7b04e6d8d52f--