[
https://issues.apache.org/jira/browse/HTRACE-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692744#comment-14692744
]
Masatake Iwasaki commented on HTRACE-69:
----------------------------------------
bq. I'm interested in how can HTrace plan to specify modules/projects tracing,
do you have existing JIRAs open for them?
This HTRACE-69 and HTRACE-214 are relevant. We need Hadoop side fix too in
follow-up.
bq. Basic MR job info are very important for us (such as container/app
lifespan), I prefer to keep them for every YARN job.
If tracing all containers/apps result in flood of tracing spans in downstream
HDFS, feature to trace specific module would be help. Currently we can trace
only YARN by loading span receiver in only YARN daemons but it means HDFS
tracing is completely turned off.
> Filtering child spans by sampler
> --------------------------------
>
> Key: HTRACE-69
> URL: https://issues.apache.org/jira/browse/HTRACE-69
> Project: HTrace
> Issue Type: New Feature
> Reporter: Masatake Iwasaki
> Assignee: Masatake Iwasaki
>
> Trace#startSpan respect the sampler given as argument only when there is no
> ongoing span (i.e. when creating new root span).
> {code}
> public static TraceScope startSpan(String description, Sampler<TraceInfo>
> s, TraceInfo tinfo) {
> Span span = null;
> if (isTracing() || s.next(tinfo)) {
> {code}
> Adding API starting span if {{(isTracing() && s.next(tinfo))}} enables
> filtering of child spans.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
