[ 
https://issues.apache.org/jira/browse/PHOENIX-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16889270#comment-16889270
 ] 

Hudson commented on PHOENIX-5358:
---------------------------------

FAILURE: Integrated in Jenkins build PreCommit-PHOENIX-Build #2818 (See 
[https://builds.apache.org/job/PreCommit-PHOENIX-Build/2818/])
PHOENIX-5358: Metrics for the GlobalIndexChecker coprocessor (s.kadam: rev 
93b58e14478e58822b05af4fc4a0afb15ad5fcb2)
* (add) 
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/metrics/GlobalIndexCheckerSource.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/metrics/MetricsIndexerSourceFactory.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/index/GlobalIndexChecker.java
* (add) 
phoenix-core/src/main/java/org/apache/phoenix/hbase/index/metrics/GlobalIndexCheckerSourceImpl.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)

Reply via email to