[
https://issues.apache.org/jira/browse/HDDS-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jitendra Nath Pandey updated HDDS-1017:
---------------------------------------
Fix Version/s: 0.4.0
> Use distributed tracing to indentify performance problems in Ozone
> ------------------------------------------------------------------
>
> Key: HDDS-1017
> URL: https://issues.apache.org/jira/browse/HDDS-1017
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.4.0
>
> Attachments: HDDS-1017.001.patch, HDDS-1017.002.patch,
> HDDS-1017.003.patch, HDDS-1017.004.patch, HDDS-1017.005.patch,
> HDDS-1017.006.patch, HDDS-1017.007.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
