[
https://issues.apache.org/jira/browse/HIVE-9756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741750#comment-14741750
]
Sergey Shelukhin commented on HIVE-9756:
----------------------------------------
Don't recall. This patch needs testing. I looked at some old logs and I see
these example threads (I removed dups by number) that have attempt ID from NDC
(note that some Tez threads also add it to thread name but that's a separate
thing)
{noformat}
ExecutionCompletionThread #0
Fetcher [Map_1] #20
IO-Elevator-Thread-0
IPC Server handler 0 on 15001
Initializer 0
New I/O worker #2
Task-Executor-0
TezTaskEventRouter[attempt_1435700346116_2494_1_01_000000_0]
TezTaskRunner_attempt_1435700346116_2494_1_00_000000_0
Wait-Queue-Scheduler-0
ShuffleAndMergeRunner [Map_1]
{noformat}
> LLAP: use log4j 2 for llap
> --------------------------
>
> Key: HIVE-9756
> URL: https://issues.apache.org/jira/browse/HIVE-9756
> Project: Hive
> Issue Type: Sub-task
> Reporter: Gunther Hagleitner
> Assignee: Prasanth Jayachandran
> Attachments: HIVE-9756.1.patch, HIVE-9756.2.patch
>
>
> For the INFO logging, we'll need to use the log4j-jcl 2.x upgrade-path to get
> throughput friendly logging.
> http://logging.apache.org/log4j/2.0/manual/async.html#Performance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
