[
https://issues.apache.org/jira/browse/HDDS-1214?focusedWorklogId=207195&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-207195
]
ASF GitHub Bot logged work on HDDS-1214:
----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Mar/19 14:25
Start Date: 04/Mar/19 14:25
Worklog Time Spent: 10m
Work Description: elek commented on pull request #550: HDDS-1214. Enable
tracing for the datanode read/write path
URL: https://github.com/apache/hadoop/pull/550
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.
See: https://issues.apache.org/jira/browse/HDDS-1214
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 207195)
Time Spent: 10m
Remaining Estimate: 0h
> 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
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
