[
https://issues.apache.org/jira/browse/HBASE-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748304#comment-13748304
]
stack commented on HBASE-8803:
------------------------------
I did some testing this evening. Had to change how HBaseAdmin is created to
make it work (it was erroring out w/ a reflection error -- it looks like can't
pass in a Configuration anymore, needs a Connection... a recent addition). I
first create connection, pass it to HBA, then make sure I close it w/
begin/ensure:
> + connection = HConnectionManager.createConnection(config)
> + begin
> + admin = HBaseAdmin.new(config)
....
So, JMS, why does it not move regions back exactly as it found them? Do you
know? Each time I ran the test, the new layout was different from the
original. It use to restore to original state IIRC.
I tried w/ two threads and it indeed ran faster (sweet).
> 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: 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
