hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sameet Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-13316) Reduce the downtime on planned moves of regions
Date Thu, 26 Mar 2015 18:11:53 GMT

     [ https://issues.apache.org/jira/browse/HBASE-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Sameet Agarwal updated HBASE-13316:
    Attachment: PlannedFailover-v2.patch

Thanks Ted for the comments. Fixed up the Javadoc issues and the unused variable. 

The synchronous call to warmup is happening in move which is an admin cmd. I am not sure it
is worth adding a config option to do/not do warmup

Also adding https://reviews.facebook.net/differential/diff/187245/ for review. 

> 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
>         Attachments: PlannedFailover-v1.patch, PlannedFailover-v2.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

View raw message