[
https://issues.apache.org/jira/browse/HBASE-13316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sameet Agarwal updated HBASE-13316:
-----------------------------------
Attachment: PlannedFailover-v1.patch
Changes based on comments:
- Moved the warmup out of the balancer function to Admin.move. The warmup is
synchronous and will take some time to complete. Having it in balance would
affect the time it takes to do large scale balancing. move happens only one
region at a time. This makes it slower but with less disruption
- Added a test to warmup a region and also move regions at the same time to see
if there are no issues doing them simultaneously
- Also fixed Findbugs and Checkstyle issues
> 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.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)
