[
https://issues.apache.org/jira/browse/HBASE-20654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16497410#comment-16497410
]
Josh Elser commented on HBASE-20654:
------------------------------------
{quote}Please say more than this. Counts of RITs makes sense as a metric and to
expose as JMX or even stuff like longest RIT.
{quote}
+1 I agree with Stack here. At most, we could include a list of tables which
have RITs in JMX. I think we should be trying to provide information to alert
admins that there is a problem through JMX not trying to provide information
that would let someone fully debug a cluster problem (e.g. user reports to
admin "my jobs are timing out", admin checks JMX "Oh, the table your job
queries has an RIT", admin digs to take action and user waits patiently)
> 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: 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)
