hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-8213) DFSClient should use hdfs.client.htrace HTrace configuration prefix rather than hadoop.htrace
Date Fri, 24 Apr 2015 22:55:40 GMT

    [ https://issues.apache.org/jira/browse/HDFS-8213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14511954#comment-14511954
] 

Nick Dimiduk commented on HDFS-8213:
------------------------------------

bq. Another very important use case of tracing is "I have proprietary app X that talks to
HDFS, and it's slow. How come?"

Bingo! That's the perspective I was missing. I hadn't considered a proprietary app market
around these tools; being a consumer of some app running on my cluster and wanting visibility
into it w/o the app supporting tracing explicitly. Thanks [~cmccabe]! Please socialize this
idea more widely ;)

> 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)

Mime
View raw message