[
https://issues.apache.org/jira/browse/HBASE-20654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16497531#comment-16497531
]
liubangchen commented on HBASE-20654:
-------------------------------------
When hbase as a PAAS service,users can not login any server.But when
regionserver restart or crash some region may me in state failed open or failed
close ,then client will get exception NotServingRegionException . But it very
difficult to find these failed open regions with out use hbck . We hope quickly
find these failded open or failed close and show at web console in order to
assign these regions again by users .
We gather metrics by GangliaSink31 or jmx , and our case as follow:
!1.png!
logs on server
{code:java}
2017-07-08 08:43:54,821 WARN [AM.-pool1-t138] master.RegionStates: Failed to
open/close 3ecca5a149b8813ce97cd97629775f07 on
emr-10-112-99-101,16010,1497344643126, set to FAILED_CLOSE
2017-07-08 08:43:54,821 WARN [AM.-pool1-t130] master.RegionStates: Failed to
open/close 4535a4fb157ccff13e5da275cc79a952 on
emr-10-112-99-101,16010,1497344643126, set to FAILED_CLOSE
{code}
> Expose regions in transition thru JMX
> -------------------------------------
>
> Key: HBASE-20654
> URL: https://issues.apache.org/jira/browse/HBASE-20654
> Project: HBase
> Issue Type: Improvement
> Reporter: Ted Yu
> Assignee: liubangchen
> Priority: Major
> Attachments: 1.png, HBASE-20654-1.patch, HBASE-20654-2.patch,
> HBASE-20654-3.patch
>
>
> Currently only the count of regions in transition is exposed thru JMX.
> Here is a sample snippet of the /jmx output:
> {code}
> {
> "beans" : [ {
> ...
> }, {
> "name" : "Hadoop:service=HBase,name=Master,sub=AssignmentManager",
> "modelerType" : "Master,sub=AssignmentManager",
> "tag.Context" : "master",
> ...
> "ritCount" : 3
> {code}
> It would be desirable to expose region name, state for the regions in
> transition as well.
> We can place configurable upper bound on the number of entries returned in
> case there're a lot of regions in transition.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
