[
https://issues.apache.org/jira/browse/HDDS-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807621#comment-16807621
]
Elek, Marton commented on HDDS-1153:
------------------------------------
[[email protected]] 100% agree. This solution is more like a proof of concept.
We can show here how OT can be used in hadoop. Would be great to get a
consensus in HADOOP-15566 and implement something in hadoop common.
In fact I am happy to migrate ozone to use any other library instead of OT in
case of an agreement in HADOOP-15566. Until that we can continue to learn from
this experiment.
> Make tracing instrumentation configurable
> -----------------------------------------
>
> Key: HDDS-1153
> URL: https://issues.apache.org/jira/browse/HDDS-1153
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Elek, Marton
> Assignee: Kitti Nanasi
> Priority: Major
> Labels: newbie, pull-request-available
> Attachments: HDDS-1153.001.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> TracingUtil.createProxy is a helper method to create a proxy instance with
> tracing support.
> The proxy instance implements the same interface as the original class and
> delegates all the method calls to the original instance but it also sends
> tracing information to the tracing server.
> By default it's not a big overhead as the tracing libraries can be configured
> to send tracing only with some low probability.
> But to make it more safe we can make it optional. With a global
> 'hdds.tracing.enabled' configuration variable (can be true by default) we can
> adjust the behavior of TracingUtil.createProxy.
> If the tracing is disabled the TracingUtil.createProxy should return with the
> 'delegate' parameter instead of a proxy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
