[
https://issues.apache.org/jira/browse/PHOENIX-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16868754#comment-16868754
]
Priyank Porwal commented on PHOENIX-5358:
-----------------------------------------
+1 to metrics from write path for phase3 for both mutable as well as immutables
indexes. A different Jira or just including them all in this Jira - either way
would be fine.
[~kozdemir] Are there other cases we want to track? e.g. a metrics to track
upsert failures caused by Phase1 index-write failures could be interesting
> Metrics for the GlobalIndexChecker coprocessor
> ----------------------------------------------
>
> Key: PHOENIX-5358
> URL: https://issues.apache.org/jira/browse/PHOENIX-5358
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.13.1, 5.0.0, 4.15.0, 4.14.2
> Reporter: Kadir OZDEMIR
> Priority: Major
>
> The GlobalIndexChecker coprocessor is responsible for checking if an index
> row is "verified", that is, has completed its most recent two-phase write
> operation, during scans. If the row is not verified then the coprocessor
> rebuilds the row using a read-repair technique. The read-repair operations
> should be rare but add extra latency on the scan operations. We need to know
> how many read-repair operations happen and how long they take. Thus, we need
> metrics on them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
