[
https://issues.apache.org/jira/browse/CASSANDRA-9507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402754#comment-15402754
]
Nachiket Patil commented on CASSANDRA-9507:
-------------------------------------------
Hi [~ifesdjeen], I had uploaded patches but didn't check if the status of the
JIRA changed to Patch Available. The patches you are looking at are correct.
The Latency is added in the RangeCommandIterator::close() method which is for
reading complete range. Not sure we should be measuring individual read.
I agree this is not a critical patch. We are not patching only 2.1 branch with
non-critical fixes right? We can still get this patch in 2.2, 3.0 - trunk.
> range metrics are not updated for timeout and unavailable in StorageProxy
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-9507
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9507
> Project: Cassandra
> Issue Type: Bug
> Components: Observability
> Reporter: sankalp kohli
> Assignee: Nachiket Patil
> Priority: Minor
> Attachments: CASANDRA-9507 trunk.diff, CASSANDRA-9507 v2.1.diff,
> CASSANDRA-9507 v2.2.diff, CASSANDRA-9507 v3.0.diff
>
>
> Looking at the code, it looks like range metrics are not updated for timeouts
> and unavailable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
