[
https://issues.apache.org/jira/browse/HBASE-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741344#comment-13741344
]
stack commented on HBASE-8803:
------------------------------
I saw this when testing against trunk:
2013-08-15 11:52:49,257 INFO [main] region_mover: Moving 12 region(s) from
a2436.halxg.cloudera.com,60020,1376590362978 during this cycle
2013-08-15 11:52:49,258 INFO [main] region_mover: Moving region
5999eb4e59af7711ea82ea37a9cc9d44 (1 of 12) to
server=10.20.212.36,60020,1376590920619
NameError: no method 'toString' for arguments
(org.apache.hadoop.hbase.TableName) on Java::OrgApacheHadoopHbaseUtil::Bytes
getTable at /home/stack/hbase-0.95.2-SNAPSHOT/bin/region_mover.rb:63
isSuccessfulScan at /home/stack/hbase-0.95.2-SNAPSHOT/bin/region_mover.rb:120
unloadRegions at /home/stack/hbase-0.95.2-SNAPSHOT/bin/region_mover.rb:334
call at org/jruby/RubyProc.java:270
call at org/jruby/RubyProc.java:224
which seems to have broke its ability to reload.
Let me move this out of 0.95.2 and put it against 0.96.0. It is not a blocker
but really important addition so it should not hold up release -- it can go in
anytime.
Thanks for working on this [~jmspaggi]
> 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
> Priority: Critical
> 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
