You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@gobblin.apache.org by "Joel Baranick (JIRA)" <ji...@apache.org> on 2018/01/06 17:56:00 UTC

[jira] [Created] (GOBBLIN-359) Job/task info stored in MDC sometimes is incorrect

Joel Baranick created GOBBLIN-359:
-------------------------------------

             Summary: Job/task info stored in MDC sometimes is incorrect
                 Key: GOBBLIN-359
                 URL: https://issues.apache.org/jira/browse/GOBBLIN-359
             Project: Apache Gobblin
          Issue Type: Bug
            Reporter: Joel Baranick
            Assignee: Joel Baranick


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
(v6.4.14#64029)