[
https://issues.apache.org/jira/browse/CASSANDRA-15582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17052377#comment-17052377
]
Jordan West edited comment on CASSANDRA-15582 at 3/5/20, 5:48 PM:
------------------------------------------------------------------
[~rha][~djoshi] would it be helpful to start with a prioritized list of metrics
to test?
Also one test [~dcapwell] suggested is to verify the accuracy of the latency
metrics after https://issues.apache.org/jira/browse/CASSANDRA-14281 -- which
changed from aggregating on write to on read. I am planning to work on this
specific test if it's not picked up by anyone since I worked on
https://issues.apache.org/jira/browse/CASSANDRA-15213.
was (Author: jrwest):
[~rha][~djoshi] would it be helpful to start with a prioritized list of metrics
to test?
Also one test [~dcapwell] suggested is to verify the accuracy of the latency
metrics after https://issues.apache.org/jira/browse/CASSANDRA-14281 -- which
changed from aggregating on write to on read. I am planning to work on this
specific test if it's not picked up by anyone since I worked on a follow up
ticket.
> 4.0 quality testing: metrics
> ----------------------------
>
> Key: CASSANDRA-15582
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15582
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest
> Reporter: Josh McKenzie
> Assignee: Romain Hardouin
> Priority: Normal
> Fix For: 4.0-rc
>
>
> In past releases we've unknowingly broken metrics integrations and introduced
> performance regressions in metrics collection and reporting. We strive in 4.0
> to not do that. Metrics should work well!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
