[TEZ-4039] Tez should inject dag id, query id into MDC

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.10.3
• Assignee: László Bodor
• Reporter: Prasanth Jayachandran
• Created: 12/Feb/19 02:54
• Updated: 08/Jan/24 11:09
• Resolved: 26/Oct/22 04:28

Description

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

 

%d{ISO8601} %-5p [%t (%X{queryId})] %c{2}: %m%n

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. 

Issue Links

• causes: TEZ-4473 Remove pointless MDC_LOGGING message from logs if there is no custom MDC key
• is related to: TEZ-2222 Investigate moving to log4j2 for logging
• links to: GitHub Pull Request #98
• links to: GitHub Pull Request #325