[
https://issues.apache.org/jira/browse/HBASE-17427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799624#comment-15799624
]
Ted Yu edited comment on HBASE-17427 at 1/4/17 11:14 PM:
---------------------------------------------------------
Tested the patch on a cluster by successfully moving regions (including
hbase:meta) off the meta server.
was (Author: [email protected]):
Here is simple test:
{code}
include Java
print String(1.1) == (1.1).to_s
s = java.lang.String.new("1.1")
print String(1.1) == s
{code}
true is printed for the first comparison while false is printed for the second
comparison
> region_mover.rb may move region onto the same server
> ----------------------------------------------------
>
> Key: HBASE-17427
> URL: https://issues.apache.org/jira/browse/HBASE-17427
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.1.6
> Reporter: Ted Yu
> Assignee: Ted Yu
> Attachments: 17427.branch-1.v1.txt
>
>
> Intermittently, region_mover.rb got stuck waiting for region to be moved onto
> same server:
> {code}
> 2017-01-04 05:37:27,830|INFO|MainThread|machine.py:145 - run()|RuntimeError:
> Region hbase:meta,,1.1588230740 stuck on
> ctr-e88-1483482546062-0245-01-000007.x.com,16020,1483507665481,,
> newserver=ctr-e88-1483482546062-0245-01-000007.x.com,16020,1483507665481
> {code}
> This was due to the following:
> {code}
> # Make a fake servername by appending ','
> metaServer = (mtl.getMetaRegionLocation(zkw).toString() + ",").to_s
> {code}
> Note the extra comma appended to server name (as can be seen in above log)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
