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/12 06:53:00 UTC
[jira] [Updated] (HDDS-16720) Count SCR GetBlock bytes in both bytesGetBlock and localBytesGetBlock
[ https://issues.apache.org/jira/browse/HDDS-16720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gargi Jaiswal updated HDDS-16720:
---------------------------------
Summary: Count SCR GetBlock bytes in both bytesGetBlock and localBytesGetBlock (was: Short-circuit GetBlock ops are counted in both numGetBlock and numLocalGetBlock)
> Count SCR GetBlock bytes in both bytesGetBlock and localBytesGetBlock
> ---------------------------------------------------------------------
>
> Key: HDDS-16720
> URL: https://issues.apache.org/jira/browse/HDDS-16720
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Datanode
> Reporter: Elavarasan Kathirvel
> Assignee: Gargi Jaiswal
> Priority: Minor
> Labels: short-circuit-read
>
> When Short-Circuit Read (SCR) is enabled and a co-located client reads a key via the domain-socket path, {{numLocalGetBlock}} correctly increments — but {{numGetBlock}} also increments, even though SCR did not use the remote/gRPC read path.
> This makes {{numGetBlock}} unreliable for SCR validation and causes double-counting in datanode metrics.
> *Expected behavior:*
> * SCR reads should increment only {{{}numLocalGetBlock{}}}. gRPC reads should increment only {{{}numGetBlock{}}}.
> *Actual behavior:*
> * SCR reads increment both numLocalGetBlock and numGetBlock is incremented twice for one read.
--
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