[
https://issues.apache.org/jira/browse/HIVE-9756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334447#comment-15334447
]
Prasanth Jayachandran commented on HIVE-9756:
---------------------------------------------
The threadpool threads issue is still there. In most cases, we pass a single
threaded thread pool to tez for task execution. This is not a big problem with
the current patch as any thread creation will inherit the MDC.. Still it does
not cover all cases (you can run llap with the latest patch and see some log
lines without NDC attempt id goes to default file). This happens with NDC as
well. As long as tez does not spin threads on its own, I think we can fix the
issue by providing a custom executor service to tez that sets up MDC properly.
In HIVE-13258 we already pass custom executor service, I will extend that and
will put up another patch.
> LLAP: use log4j 2 for llap (log to separate files, etc.)
> --------------------------------------------------------
>
> Key: HIVE-9756
> URL: https://issues.apache.org/jira/browse/HIVE-9756
> Project: Hive
> Issue Type: Sub-task
> Affects Versions: 2.0.0
> Reporter: Gunther Hagleitner
> Assignee: Prasanth Jayachandran
> Attachments: HIVE-9756.1.patch, HIVE-9756.2.patch, HIVE-9756.3.patch,
> HIVE-9756.4.patch, HIVE-9756.4.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)
