You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Elek, Marton (JIRA)" <ji...@apache.org> on 2019/01/28 12:52:00 UTC
[jira] [Created] (HDDS-1017) Use distributed tracing the indentify
performance problems in Ozone
Elek, Marton created HDDS-1017:
----------------------------------
Summary: Use distributed tracing the indentify performance problems in Ozone
Key: HDDS-1017
URL: https://issues.apache.org/jira/browse/HDDS-1017
Project: Hadoop Distributed Data Store
Issue Type: Improvement
Reporter: Elek, Marton
Assignee: Elek, Marton
In the recent months multiple performance issues are resolved in OM/SCM and datanode sides. To identify the remaining problems a distributed tracing framework would help a lot.
In HADOOP-15566 there is an ongoing discussion to remove the discontinued HTrace and use something else instead. Until now without any conclusion, but
1). There is one existing poc in the jira which uses opentracing
2). It was suggested to "evaluating all the options" before a final decision
As an evaluation step we would like to investigate the performance of ozone components with opentracing. This patch can help us to find the performance problem but can be reverted when we will have a final solution in HADOOP-15566 about the common tracing library.
To make it lightweight we can use the ozone message level tracing identifier for context propagation instead of modifying the existing hadoop rpc framework.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org