You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Gargi Jaiswal (Jira)" <ji...@apache.org> on 2026/10/14 06:19:00 UTC
[jira] [Reopened] (HDDS-16725) SCR failure metric from design doc is not implemented
[ https://issues.apache.org/jira/browse/HDDS-16725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gargi Jaiswal reopened HDDS-16725:
----------------------------------
> SCR failure metric from design doc is not implemented
> -----------------------------------------------------
>
> Key: HDDS-16725
> URL: https://issues.apache.org/jira/browse/HDDS-16725
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Datanode
> Reporter: Elavarasan Kathirvel
> Assignee: Gargi Jaiswal
> Priority: Major
> Labels: short-circuit-read
> Fix For: 2.3.0
>
>
> As per the HDDS-10685 design document ({{{}hadoop-hdds/docs/content/design/short-circuit-read.md{}}}), Short-Circuit Read (SCR) should expose metrics for:
> * bytes read through SCR
> * successful SCR read count
> * failed SCR read count
> The current implementation only partially delivers this. The failure metric is not implemented.
>
> Short-Circuit Read (SCR) failures are not captured in any datanode or client metric. When SCR fails, the read typically falls back to gRPC and succeeds, but there is no way to monitor or validate SCR failure rate through JMX/metrics.
>
> *Expected Behavior:*
> * SCR success count, failure count, and bytes read should all be available in metrics.
> *Actual Behavior:*
> * Failure metric is missing. SCR failures are visible only in logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org