[
https://issues.apache.org/jira/browse/HBASE-25329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259327#comment-17259327
]
Bharath Vissapragada commented on HBASE-25329:
----------------------------------------------
Patch seems fine but was curious if we considered adding something like a /rit
end point (servlet) on master?
Looks like the patch caps the number of RITs to 20 and emits a new metric that
is a concatenation of hashes. IMO it is more useful to have a nice parseable
(json) end point that has richer metadata (like server ritDuration and other
RegionState attributes). It's much easier to parse this file rather than parse
a metric which is plain hashes. Thoughts?
> Dump region hashes in logs for the regions that are stuck in transition for
> more than a configured amount of time
> -----------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-25329
> URL: https://issues.apache.org/jira/browse/HBASE-25329
> Project: HBase
> Issue Type: Improvement
> Reporter: Caroline
> Assignee: Caroline
> Priority: Minor
> Attachments: HBASE-25329.branch-1.000.patch,
> HBASE-25329.branch-2.000.patch, HBASE-25329.master.000.patch
>
>
> We have metrics for number of RITs as well as number of RITs above a certain
> threshold, but we don't have any way of keeping track of the region hashes of
> those RITs. It would be beneficial to emit those region hashes as a metric,
> as well as log them, so that we don't accidentally lose this information for
> debugging the RIT at a later tiime.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
