[ https://issues.apache.org/jira/browse/TEZ-4039 ]


    László Bodor deleted comment on TEZ-4039:
    -----------------------------------

was (Author: tez-ci):
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 14m 
59s{color} | {color:red} Docker failed to build yetus/tez:474bb22ba. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| GITHUB PR | https://github.com/apache/tez/pull/98 |
| JIRA Issue | TEZ-4039 |
| Console output | 
https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-98/2/console |
| versions | git=2.17.1 |
| Powered by | Apache Yetus 0.12.0 https://yetus.apache.org |


This message was automatically generated.



> 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
>         Attachments: TEZ-4039.01.patch, TEZ-4039.02.patch, TEZ-4039.03.patch, 
> TEZ-4039.04.patch, TEZ-4039.05.patch
>
>          Time Spent: 1h
>  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)

Reply via email to