[HIVE-25585] Put dagId to MDC once it's available in HS2

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0-beta-1
• Labels: pull-request-available
• Assignee: László Bodor
• Reporter: László Bodor
• Created: 01/Oct/21 08:05
• Updated: 15/Aug/23 06:33
• Resolved: 02/Nov/22 09:00

Description

This is about putting dagID to MDC once the DAG is submitted. This way, dagId can be easily appended to log messages by log4j.
Like:

hiveserver2 <14>1 2022-10-25T10:51:05.496Z hiveserver2-0 hiveserver2 1 24a33001-3523-415b-a6a8-7733708507af [mdc@18060 class="monitoring.RenderStrategy$LogToFileFunction" dagId="dag_1666694252139_0000_3" level="INFO" operationLogLevel="EXECUTION" queryId="hive_20221025105055_ec8135b4-1b0e-46b8-bb3f-4b58b41cf53b" sessionId="6fc7adf6-d3b0-470a-813f-03c79a0ca20d" thread="HiveServer2-Background-Pool: Thread-196"] Map 1: 1/1    Map 2: 0(+11)/208    Map 7: 1/1    Map 8: 12(+11)/23    Map 9: 1/1    Reducer 3: 0/738    Reducer 4: 0/642    Reducer 5: 0/1    Reducer 6: 0/782    

Issue Links

• links to: GitHub Pull Request #3702