[jira] [Commented] (PHOENIX-5909) Table and index-level metrics for indexing coprocs

["Hadoop QA (Jira)" <ji...@apache.org>]

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

Hadoop QA commented on PHOENIX-5909:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  7s{color} | {color:red} PHOENIX-5909 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | PHOENIX-5909 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/13011979/PHOENIX-5909-4.x-v2.patch |
| Console output | https://ci-hadoop.apache.org/job/PreCommit-PHOENIX-Build/36/console |
| versions | git=2.17.1 |
| Powered by | Apache Yetus 0.12.0 https://yetus.apache.org |


This message was automatically generated.



> Table and index-level metrics for indexing coprocs
> --------------------------------------------------
>
>                 Key: PHOENIX-5909
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5909
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Geoffrey Jacoby
>            Assignee: Geoffrey Jacoby
>            Priority: Major
>             Fix For: 5.1.0, 4.16.0
>
>         Attachments: PHOENIX-5909-4.x-v1.patch, PHOENIX-5909-4.x-v2.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> For many of the metrics which the IndexRegionObserver and GlobalIndexChecker coprocs expose, it would be useful to have them broken down by table or index, in addition to the current aggregates by region server. This would help us determine if, for example, a flood of read repairs was coming from one particular index. 
> Thanks [~priyankporwal] for the feature suggestion. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)