[jira] [Commented] (HBASE-15815) Region mover script sometimes reports stuck region where only one server was involved
[
https://issues.apache.org/jira/browse/HBASE-15815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304438#comment-15304438
]
Hudson commented on HBASE-15815:
FAILURE: Integrated in HBase-0.98-matrix #348 (See
[https://builds.apache.org/job/HBase-0.98-matrix/348/])
HBASE-15815 Region mover script sometimes reports stuck region where (apurtell:
rev 8b4a2dcaf7f97015fdfdf0757f571cdd139f455f)
* bin/region_mover.rb
> 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
>Assignee: Ted Yu
>Priority: Minor
> Fix For: 1.4.0, 0.98.20
>
> Attachments: 15815-branch-1.v1.txt, 15815-branch-1.v2.txt,
> HBASE-15815.branch-1.02.txt, HBASE-15815.branch-1.v2.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)
[jira] [Commented] (HBASE-15815) Region mover script sometimes reports stuck region where only one server was involved
[
https://issues.apache.org/jira/browse/HBASE-15815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304388#comment-15304388
]
Hudson commented on HBASE-15815:
FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1220 (See
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1220/])
HBASE-15815 Region mover script sometimes reports stuck region where (apurtell:
rev 8b4a2dcaf7f97015fdfdf0757f571cdd139f455f)
* bin/region_mover.rb
> 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
>Assignee: Ted Yu
>Priority: Minor
> Fix For: 1.4.0, 0.98.20
>
> Attachments: 15815-branch-1.v1.txt, 15815-branch-1.v2.txt,
> HBASE-15815.branch-1.02.txt, HBASE-15815.branch-1.v2.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)
[jira] [Commented] (HBASE-15815) Region mover script sometimes reports stuck region where only one server was involved
[
https://issues.apache.org/jira/browse/HBASE-15815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282391#comment-15282391
]
Jerry He commented on HBASE-15815:
--
+1 on v2
> 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, 15815-branch-1.v2.txt,
> HBASE-15815.branch-1.v2.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)
[jira] [Commented] (HBASE-15815) Region mover script sometimes reports stuck region where only one server was involved
[
https://issues.apache.org/jira/browse/HBASE-15815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
