[
https://issues.apache.org/jira/browse/HDDS-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761249#comment-16761249
]
Hadoop QA commented on HDDS-1017:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 6s{color}
| {color:red} HDDS-1017 does not apply to trunk. Rebase required? Wrong Branch?
See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDDS-1017 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12957072/HDDS-1017.002.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HDDS-Build/2182/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> 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
> Priority: Major
> Labels: pull-request-available
> Attachments: HDDS-1017.001.patch, HDDS-1017.002.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]
