[
https://issues.apache.org/jira/browse/HDFS-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908033#comment-13908033
]
Masatake Iwasaki commented on HDFS-5274:
----------------------------------------
bq. Masatake Iwasaki You know, I was thinking... Maybe it ok that there are so
many spans? Tracing doesn't cost unless enabled. When debugging, you might want
to see in the trace that HDFS is doing a bunch of small reads?
I just missed your comment on uploading v.8 patch.
Because there were so many spans than I expected and receiver's queue was
filled, I think disabling those spans is safer as a starting point.
{noformat}
14/02/19 22:25:23 ERROR impl.ZipkinSpanReceiver: Error trying to append span
(DFSOutputStream.write) to the queue. Blocking Queue was full.
{noformat}
> Add Tracing to HDFS
> -------------------
>
> Key: HDFS-5274
> URL: https://issues.apache.org/jira/browse/HDFS-5274
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: datanode, namenode
> Affects Versions: 2.1.1-beta
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Attachments: HDFS-5274-0.patch, HDFS-5274-1.patch, HDFS-5274-2.patch,
> HDFS-5274-3.patch, HDFS-5274-4.patch, HDFS-5274-5.patch, HDFS-5274-6.patch,
> HDFS-5274-7.patch, HDFS-5274-8.patch, Zipkin Trace a06e941b0172ec73.png,
> Zipkin Trace d0f0d66b8a258a69.png, ss-5274v8-get.png, ss-5274v8-put.png
>
>
> Since Google's Dapper paper has shown the benefits of tracing for a large
> distributed system, it seems like a good time to add tracing to HDFS. HBase
> has added tracing using HTrace. I propose that the same can be done within
> HDFS.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
