[
https://issues.apache.org/jira/browse/HIVE-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15622634#comment-15622634
]
liyunzhang_intel edited comment on HIVE-13517 at 10/31/16 4:38 PM:
-------------------------------------------------------------------
[~szehon]:
{quote}
It would be great if there could be thread-ids in the logs.
{quote}
currently hive log4j pattern is like {noformat}
appender.DRFA.layout.pattern = %d{ISO8601} %5p [%t] %c{2}: %m%n{noformat} Here
%t means thread's name. What you want is thread-id, is my understanding right?
I'm confused that why thread-name is not more suitable than thread-id as log4j
only support thread'name not thread id.
was (Author: kellyzly):
[~szehon]:
{quote}
It would be great if there could be thread-ids in the logs.
{quote}
currently hive log4j pattern is like {noformat}
appender.DRFA.layout.pattern = %d{ISO8601} %5p [%t] %c{2}: %m%n{noformat} Here
%t means thread's name. What you want is thread-id, is my understanding right?
> Hive logs in Spark Executor and Driver should show thread-id.
> -------------------------------------------------------------
>
> Key: HIVE-13517
> URL: https://issues.apache.org/jira/browse/HIVE-13517
> Project: Hive
> Issue Type: Bug
> Components: Spark
> Affects Versions: 1.2.1, 2.0.0
> Reporter: Szehon Ho
> Assignee: liyunzhang_intel
>
> In Spark, there might be more than one task running in one executor.
> Similarly, there may be more than one thread running in Driver.
> This makes debugging through the logs a nightmare. It would be great if there
> could be thread-ids in the logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
