[jira] [Updated] (PHOENIX-5909) Table and index-level metrics for indexing coprocs
[ https://issues.apache.org/jira/browse/PHOENIX-5909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby updated PHOENIX-5909: - Attachment: PHOENIX-5909.master.v1.patch > 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, > PHOENIX-5909.master.v1.patch > > Time Spent: 0.5h > 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)
[jira] [Updated] (PHOENIX-5909) Table and index-level metrics for indexing coprocs
[ https://issues.apache.org/jira/browse/PHOENIX-5909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby updated PHOENIX-5909: - Attachment: PHOENIX-5909-4.x-v2.patch > 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)
[jira] [Updated] (PHOENIX-5909) Table and index-level metrics for indexing coprocs
[ https://issues.apache.org/jira/browse/PHOENIX-5909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoffrey Jacoby updated PHOENIX-5909: - Attachment: PHOENIX-5909-4.x-v1.patch > 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 > > Time Spent: 10m > 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)
