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

Hadoop QA commented on PHOENIX-5358:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12975124/PHOENIX-5358.4.x-HBase-1.3.v1.patch
  against 4.x-HBase-1.3 branch at commit 
6a7115c2862ae90b4d200057a0523a5fb4163fa7.
  ATTACHMENT ID: 12975124

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-PHOENIX-Build/2808//console

This message is automatically generated.

> 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.v1.patch, 
> PHOENIX-5358.master.v1.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