Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 05643179C4 for ; Fri, 27 Mar 2015 22:49:01 +0000 (UTC) Received: (qmail 24058 invoked by uid 500); 27 Mar 2015 22:48:54 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 24019 invoked by uid 500); 27 Mar 2015 22:48:54 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 24008 invoked by uid 99); 27 Mar 2015 22:48:54 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Mar 2015 22:48:54 +0000 Date: Fri, 27 Mar 2015 22:48:54 +0000 (UTC) From: "Elliott Clark (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-13316) Reduce the downtime on planned moves of regions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384838#comment-14384838 ] Elliott Clark commented on HBASE-13316: --------------------------------------- It's a large replication test; those are always a little flakey since it has to spin up two full clusters. I'll run it a few times locally to see if this changed with this commit. > Reduce the downtime on planned moves of regions > ----------------------------------------------- > > Key: HBASE-13316 > URL: https://issues.apache.org/jira/browse/HBASE-13316 > Project: HBase > Issue Type: Improvement > Components: Balancer > Affects Versions: 2.0.0, 1.0.1, 1.1.1 > Reporter: Sameet Agarwal > Assignee: Sameet Agarwal > Priority: Minor > Fix For: 2.0.0, 1.1.0 > > Attachments: PlannedFailover-v1.patch, PlannedFailover-v2.patch, PlannedFailover-v3.patch, PlannedFailover.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > The current behavior of a region move shuts down a region and then starts is up in another regionserver. This causes increased latency and possibly timeouts till the new region's cache is fully warmed up. We can make a region move less disruptive by warming the cache in the destination region server before shutting dow the old region. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)