[
https://issues.apache.org/jira/browse/HDDS-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763474#comment-16763474
]
Elek, Marton edited comment on HDDS-1017 at 2/8/19 10:43 AM:
-------------------------------------------------------------
[~bharatviswa]. That was a merge conflict.
I prefer to exclude okhttp from the http-client as jaeger uses the okhttp
client, but (AFAIK) we don't use any part from hdfs-client which depends from
the okhttp.
The problem was the rebase: the HDDS-922 introduced a new dependency to use
hdfs-client. Now I excluded the okhttp from the newly introduced dependency and
everything worked fine.
The remaining tests are not related. As there were no real changes since the
last +1 from [~anu], I will commit this to the trunk (without the one remaining
unused import).
was (Author: elek):
[~bharatviswa]. That was a merge conflict.
I prefer to exclude okhttp from the http-client as jaeger uses the okhttp
client, but (AFAIK) we don't use any part from hdfs-client which depends from
the okhttp.
The problem was the rebase: the HDDS-922 introduced a new dependency to use
hdfs-client. Now I excluded the okhttp from the newly introduced dependency and
everything worked fine.
The remaining tests are not related. As there was no real changes since the
last +1 from [~anu], I will commit this to the trunk (without the one remaining
unused import).
> 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: Improvement
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Labels: pull-request-available
> 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: 10m
> 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]
