accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4192) Analyze Threading for Tracing correctness
Date Sat, 16 Apr 2016 22:04:25 GMT


Josh Elser commented on ACCUMULO-4192:

bq. I think the removal of that TraceRunnable was fixing a bug

Sorry, I wasn't suggesting that we should reinstate it, but that we should check for {{Trace.wrap}}
in the appropriate places. Would that cause more problems, [~billie.rinaldi]? I'm trying to
remember the details of ACCUMULO-3507.

> Analyze Threading for Tracing correctness
> -----------------------------------------
>                 Key: ACCUMULO-4192
>                 URL:
>             Project: Accumulo
>          Issue Type: Task
>          Components: trace
>            Reporter: Josh Elser
>            Priority: Blocker
>             Fix For: 1.7.2, 1.8.0
> When we switched from cloudtrace to htrace, we lost an implicit {{TraceRunnable}} wrapper
in NamingThreadFactory (which is used by SimpleThreadPool). This results in the current Trace's
span being lost across threads.
> We should inspect uses of SimpleThreadPool (and maybe TraceRunnable in 1.6) to make sure
that we don't have any other hidden tracing problems before the next 1.7 and 1.8 release.

This message was sent by Atlassian JIRA

View raw message