You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2016/04/17 23:47:25 UTC
[jira] [Updated] (ACCUMULO-4192) Analyze Threading for Tracing
correctness
[ https://issues.apache.org/jira/browse/ACCUMULO-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Tubbs updated ACCUMULO-4192:
----------------------------------------
Fix Version/s: (was: 1.7.2)
(was: 1.8.0)
> Analyze Threading for Tracing correctness
> -----------------------------------------
>
> Key: ACCUMULO-4192
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4192
> Project: Accumulo
> Issue Type: Task
> Components: trace
> Reporter: Josh Elser
> Priority: Blocker
>
> 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
(v6.3.4#6332)