[jira] [Commented] (TEZ-4039) Tez should inject dag id, query id into MDC

["László Bodor (Jira)" <ji...@apache.org>]

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

László Bodor commented on TEZ-4039:
-----------------------------------

addendum merged to master before releasing 0.10.3
https://github.com/apache/tez/commit/174d0d13f7809e881986364511fe129861165a61

thanks [~ayushtkn] for taking care of this!

> Tez should inject dag id, query id into MDC
> -------------------------------------------
>
>                 Key: TEZ-4039
>                 URL: https://issues.apache.org/jira/browse/TEZ-4039
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Prasanth Jayachandran
>            Assignee: László Bodor
>            Priority: Major
>             Fix For: 0.10.3
>
>         Attachments: TEZ-4039.01.patch, TEZ-4039.02.patch, TEZ-4039.03.patch, TEZ-4039.04.patch, TEZ-4039.05.patch
>
>          Time Spent: 4.5h
>  Remaining Estimate: 0h
>
> Tez currently uses CallableWithNdc to store thread specific context. It should also inject the context into MDC so that pattern layout can dump the contexts from MDC (with NDC it is not possible to read the context in pattern lyaout).
> Hive for example, sets queryId in the MDC and pattern layout prints the queryId
>  
> {code:java}
> %d{ISO8601} %-5p [%t (%X{queryId})] %c{2}: %m%n
> {code}
> Llap sets dagId, fragmentId and queryId into MDC which is used for queryId based routing of logging.
> Similarly, Tez AM should set dagId and queryId (if available) into MDC. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)