accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4192) Analyze Threading for Tracing correctness
Date Mon, 18 Apr 2016 15:39:25 GMT

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

Christopher Tubbs commented on ACCUMULO-4192:
---------------------------------------------

Ah, I briefly wondered if that might be the case, but quickly figured it was probably just
overlooked. Still, I think it's probably better in the comments or on the history of the issue,
or maybe even in the affectsVersion so it doesn't produce confusing JIRA search results. Whatever
you think is best. If you change it back, it won't matter to me.

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

Mime
View raw message