[
https://issues.apache.org/jira/browse/PHOENIX-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16889124#comment-16889124
]
Hudson commented on PHOENIX-5358:
---------------------------------
SUCCESS: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #503 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/503/])
PHOENIX-5358: Metrics for the GlobalIndexChecker coprocessor (s.kadam: rev
9da113f7335c953537c1498cbedaef7758fb3ce6)
* (add)
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/metrics/GlobalIndexCheckerSourceImpl.java
* (add)
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/metrics/GlobalIndexCheckerSource.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/index/GlobalIndexChecker.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/metrics/MetricsIndexerSourceFactory.java
> 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
> Assignee: Priyank Porwal
> Priority: Major
> Fix For: 4.15.0, 5.1.0, 4.14.3
>
> Attachments: PHOENIX-5358.4.x-HBase-1.3.v2.patch,
> PHOENIX-5358.master.v4.patch
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> 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.14#76016)
