[
https://issues.apache.org/jira/browse/HDDS-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762877#comment-16762877
]
Bharat Viswanadham commented on HDDS-1017:
------------------------------------------
There were some test failures related to the patch.
{code:java}
org.apache.hadoop.ozone.container.ozoneimpl.TestOzoneContainer.testCloseContainer
Failing for the past 1 build (Since #2194 ) Took 2.3 sec. Error Message
There is already a current global Tracer registered.
Stacktrace
java.lang.IllegalStateException: There is already a current global Tracer
registered. at io.opentracing.util.GlobalTracer.register(GlobalTracer.java:107)
at org.apache.hadoop.hdds.tracing.TracingUtil.initTracing(TracingUtil.java:48)
at
org.apache.hadoop.ozone.HddsDatanodeService.start(HddsDatanodeService.java:156)
at
org.apache.hadoop.ozone.MiniOzoneClusterImpl.lambda$startHddsDatanodes$2(MiniOzoneClusterImpl.java:353)
at java.util.ArrayList.forEach(ArrayList.java:1257) at
org.apache.hadoop.ozone.MiniOzoneClusterImpl.startHddsDatanodes(MiniOzoneClusterImpl.java:353)
at
org.apache.hadoop.ozone.MiniOzoneClusterImpl$Builder.build(MiniOzoneClusterImpl.java:391)
at
org.apache.hadoop.ozone.container.ozoneimpl.TestOzoneContainer.testCloseContainer(TestOzoneContainer.java:296)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
{code}
> 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
>
> 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]
