[jira] [Updated] (GOBBLIN-359) Logged Job/Task info from TaskExecutor threads sometimes does not match the task running

["Abhishek Tiwari (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GOBBLIN-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Abhishek Tiwari updated GOBBLIN-359:
------------------------------------
    Fix Version/s: 0.12.0

> Logged Job/Task info from TaskExecutor threads sometimes does not match the task running
> ----------------------------------------------------------------------------------------
>
>                 Key: GOBBLIN-359
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-359
>             Project: Apache Gobblin
>          Issue Type: Bug
>            Reporter: Joel Baranick
>            Assignee: Joel Baranick
>            Priority: Major
>             Fix For: 0.12.0, 0.13.0
>
>
> In some cases the job/task information that is stored in the MDC to improve logging doesn't match the actual task being run on a given thread.  It seems as if the MDC contents are not always being managed in a way that ensures that when a task is complete the MDC data is cleared.
> One place I noticed was in {{TaskExecutor}}, where {{this.taskExecutor}} and {{this.forkExecutor}} are not wrapped with {{ExecutorUtils.loggingDecorator}}.  {{ExecutorUtils.loggingDecorator}} ensures that submitted {{Runnable}} and {{Callable}} instances first clone the MDC and finally reset the MDC.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)