Elek, Marton created HDDS-1214:
----------------------------------
Summary: Enable tracing for the datanode read/write path
Key: HDDS-1214
URL: https://issues.apache.org/jira/browse/HDDS-1214
Project: Hadoop Distributed Data Store
Issue Type: Improvement
Components: Ozone Datanode
Reporter: Elek, Marton
Assignee: Elek, Marton
HDDS-1150 introduced distributed for ozone components. But we have no trace
context propagation between the clients and Ozone Datanodes.
As we use Grpc and Ratis on this RPC path the full tracing could be quite
complex: we should propagate the trace id in Ratis and include it in all the
log entries.
I propose a simplified solution here: to trace only the StateMachine operations.
As Ratis is a library we provide the implementation of the appropriate Raft
elements especially the StateMachine and the raft messages. We can add the
tracing information to the raft messages (in fact, we already have this field)
and we can restore the tracing context during the StateMachine operations.
This approach is very simple (only a few lines of codes) and can show the time
of the real write/read operations, but can't see the internals of the Ratis
operations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
