[
https://issues.apache.org/jira/browse/HDFS-8213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514721#comment-14514721
]
Colin Patrick McCabe commented on HDFS-8213:
--------------------------------------------
bq. What that doesn't clarify to me is how I would connect the dots of spans
initiated within the HDFSClient back to actions takes by said app.
It depends on what we're trying to do. For example, we may be getting reports
that the cluster is slow. In this case, seeing that HDFS / HBase requests
complete quickly allows us to focus on other systems in the stack.
Ultimately, the best thing will always be to have tracing in every app. But it
will take a while to get there and having the ability to get useful results out
of incremental steps is really useful.
> DFSClient should use hdfs.client.htrace HTrace configuration prefix rather
> than hadoop.htrace
> ---------------------------------------------------------------------------------------------
>
> Key: HDFS-8213
> URL: https://issues.apache.org/jira/browse/HDFS-8213
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.7.0
> Reporter: Billie Rinaldi
> Assignee: Colin Patrick McCabe
> Priority: Critical
> Attachments: HDFS-8213.001.patch
>
>
> DFSClient initializing SpanReceivers is a problem for Accumulo, which manages
> SpanReceivers through its own configuration. This results in the same
> receivers being registered multiple times and spans being delivered more than
> once. The documentation says SpanReceiverHost.getInstance should be issued
> once per process, so there is no expectation that DFSClient should do this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
