[
https://issues.apache.org/jira/browse/HADOOP-11758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384334#comment-14384334
]
Colin Patrick McCabe commented on HADOOP-11758:
-----------------------------------------------
Hmm. The idea behind HTrace is not to trace every operation. We should be
tracing less than 1% of all operations At that point, we wouldn't really have
a problem with too many trace spans.
The only time you would turn on tracing for every operation is when doing
debugging. In that case it's like turning log4j up to TRACE level-- you know
you're going to get swamped.
So basically I would argue that we already do have an option to filter out too
many trace spans-- setting the trace sampler to ProbabilitySampler.
> Add options to filter out too much granular tracing spans
> ---------------------------------------------------------
>
> Key: HADOOP-11758
> URL: https://issues.apache.org/jira/browse/HADOOP-11758
> Project: Hadoop Common
> Issue Type: Improvement
> Components: tracing
> Reporter: Masatake Iwasaki
> Assignee: Masatake Iwasaki
> Priority: Minor
> Attachments: testWriteTraceHooks.html
>
>
> in order to avoid queue in span receiver spills
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
