rajesh created HDDS-17761:
-----------------------------

             Summary: Tracing improvements for Ozone client
                 Key: HDDS-17761
                 URL: https://issues.apache.org/jira/browse/HDDS-17761
             Project: Apache Ozone
          Issue Type: Task
            Reporter: rajesh
            Assignee: rajesh


A client trace today is a root span for the command plus the OM and datanode 
RPC spans. The root span name contains the full argument list, so every new 
path becomes a new operation in Jaeger. Most of the client's own work on the 
data path is not visible, and a failure does not show which datanode was 
involved.

Close that gap for ozone sh, ozone fs and the Ozone client key read and write 
path:
* The root span is named by the command (for example "ozone sh key put"). The 
arguments are recorded as redacted attributes, together with the volume, 
bucket, key, data size and replication.
* Writes show the time until the datanode replies, not only until the request 
is sent. They record bytes and blocks written and the number of write retries.
* Reads have a span per block request, and the datanode side of a streaming 
read joins the same trace.
* Each datanode call records which datanode served it. When the client fails 
over, each datanode failure is recorded.
* One-time client setup has its own spans: datanode connection, client metrics 
start-up, security configuration, and block flush.

Depends on HDDS-17581. Reuses the same tracing helpers as HDDS-17586. No 
separate proxy, attribute or local-span sub-tasks.

Out of scope: OM (HDDS-17586), SCM (HDDS-17593), datanode (HDDS-17594), and 
Freon, which gets its own task.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to