[
https://issues.apache.org/jira/browse/HBASE-14749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995024#comment-14995024
]
Abhishek Singh Chouhan commented on HBASE-14749:
------------------------------------------------
[~stack] When trying to move regions to master, the move is simply ignored.
DEBUG [B.defaultRpcServer.handler=0,queue=0,port=55490] master.HMaster(1422):
Skipping move of region
testRegionMover,m,1446869600631.81c5fbb05ca7c972a32b6cd858168cd6. to avoid
unnecessary region moving later by load balancer, because it should not be on
master
To skip this situation, added the stripMaster method to remove master from
coming in list of move targets. However if the master is not there in the list
simply log the warning like the one you got (maybe i should remove "Error
removing master..") and go on to moving regions. In your case too the move
should have succeeded, just that this warning is also logged if master was not
there in the list of RS. This won't cause any failures. I din't try on a
branch-1 cluster but i tested out on a cluster of VMs running on 2.0.
> Make changes to region_mover.rb to use RegionMover Java tool
> ------------------------------------------------------------
>
> Key: HBASE-14749
> URL: https://issues.apache.org/jira/browse/HBASE-14749
> Project: HBase
> Issue Type: Improvement
> Reporter: Abhishek Singh Chouhan
> Assignee: Abhishek Singh Chouhan
> Fix For: 2.0.0
>
> Attachments: HBASE-14749.patch, HBASE-14749.patch
>
>
> With HBASE-13014 in, we can now replace the ruby script such that it invokes
> the Java Tool. Also expose timeout and no-ack mode which were added.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
