[
https://issues.apache.org/jira/browse/HBASE-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748468#comment-13748468
]
Jean-Marc Spaggiari commented on HBASE-8803:
--------------------------------------------
Hi Stack,
Do we need to move those modifications to 0.94 too?
Like
{quote}
TableName::META_TABLE_NAME.getName()
{quote}
etc.?
Regions names are stored locally into movedRegions and a file when removed from
one server, and then the same list is used to restore the regions. So you
should have exactly the same lost before and after the restart... I will re-try
that over the week-end and check the regions, not just the count...
> region_mover.rb should move multiple regions at a time
> ------------------------------------------------------
>
> Key: HBASE-8803
> URL: https://issues.apache.org/jira/browse/HBASE-8803
> Project: HBase
> Issue Type: Bug
> Components: Usability
> Affects Versions: 0.98.0, 0.94.8, 0.95.1
> Reporter: Jean-Marc Spaggiari
> Assignee: Jean-Marc Spaggiari
> Fix For: 0.98.0, 0.94.12, 0.96.0
>
> Attachments: 8803v5.txt, HBASE-8803-v0-trunk.patch,
> HBASE-8803-v1-0.94.patch, HBASE-8803-v1-trunk.patch,
> HBASE-8803-v2-0.94.patch, HBASE-8803-v2-0.94.patch, HBASE-8803-v3-0.94.patch,
> HBASE-8803-v4-0.94.patch, HBASE-8803-v4-trunk.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> When there is many regions in a cluster, rolling_restart can take hours
> because region_mover is moving the regions one by one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
