[
https://issues.apache.org/jira/browse/HDDS-16918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18146028#comment-18146028
]
Gargi Jaiswal commented on HDDS-16918:
--------------------------------------
[@Elavarasan Kathirvel|https://cloudera.enterprise.slack.com/team/U03TY4S0RDF]
this is not a problem if SCR falls back to grpc then the log is not visible on
the datanode. Client side the error is visible means on the terminal when u are
running freon command there u can find :
{{ERROR … DomainSocketFactory: Failed to create DomainSocketERROR …
DomainSocketFactory: /path/to/socket is disabled for … ms due to current
failureWARN … BlockInputStream: Failed to acquire short-circuit reads client …
Fallback to Grpc client.}}
When u are running freon command for short-circuit read there itself u can find
the error or warn message stating {{falling back to grpc}} . These should be
shown on client side (in ur case {{shell}} will display message) not on the
datanode side.
> Short-Circuit Read domain socket failure silently falls back to gRPC without
> logging on DataNode
> ------------------------------------------------------------------------------------------------
>
> Key: HDDS-16918
> URL: https://issues.apache.org/jira/browse/HDDS-16918
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Datanode
> Reporter: Elavarasan Kathirvel
> Assignee: Gargi Jaiswal
> Priority: Major
> Labels: short-circuit-read
>
> When Short-Circuit Read (SCR) is enabled and the UNIX domain socket is
> altered or missing (e.g., renamed/deleted), the read request correctly falls
> back to standard gRPC. However, the failure to establish or access the
> Short-Circuit Read path is not captured in the DataNode logs.
> h4. Steps to Reproduce
> # Configure and enable Short-Circuit Read on the Ozone cluster.
> # Start an Ozone client on the same host as a DataNode.
> # Rename or delete the UNIX domain socket file used for Short-Circuit Read.
> # Execute a key read operation from the local client on that DataNode.
> h4. Actual Result
> The key read operation succeeds by falling back to standard gRPC read path.
> However, the DataNode log contains no {{WARN}} or {{ERROR}} messages
> indicating that the Short-Circuit Read attempt failed due to a
> missing/unreachable domain socket.
> h4. Expected Result
> When a Short-Circuit Read path attempt fails, the DataNode (or
> Client/DataNode interface) should log a descriptive {{WARN}} message
> detailing the domain socket failure (e.g., {{SocketException}} /
> {{FileNotFoundException}} for the socket path) prior to initiating the gRPC
> fallback.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]