[ https://issues.apache.org/jira/browse/HBASE-15815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282320#comment-15282320 ]
Jerry He commented on HBASE-15815: ---------------------------------- You don't want to use the getRegionNameAsString(), which is used in the next logging? Looks good other than that. > Region mover script sometimes reports stuck region where only one server was > involved > ------------------------------------------------------------------------------------- > > Key: HBASE-15815 > URL: https://issues.apache.org/jira/browse/HBASE-15815 > Project: HBase > Issue Type: Bug > Affects Versions: 1.1.2 > Reporter: Ted Yu > Priority: Minor > Attachments: 15815-branch-1.v1.txt > > > Sometimes we saw the following in output from region mover script: > {code} > 2016-05-11 01:38:21,187||INFO|3969|140086696048384|MainThread|2016-05-11 > 01:38:21,186 INFO [RubyThread-7: > /.../current/hbase-client/bin/thread-pool.rb:28-EventThread] > zookeeper.ClientCnxn: EventThread shut down > 2016-05-11 01:38:21,299||INFO|3969|140086696048384|MainThread|RuntimeError: > Region stuck on hbase-5-2.osl,16020,1462930100540,, > newserver=hbase-5-2.osl,16020,1462930100540 > {code} > There was only one server involved. > Since the name of region was not printed, it makes debugging hard to do. -- This message was sent by Atlassian JIRA (v6.3.4#6332)