[ 
https://issues.apache.org/jira/browse/HIVE-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933954#comment-15933954
 ] 

liyunzhang_intel commented on HIVE-13517:
-----------------------------------------

[~stakiar]: it is ok to assign it to you.
what i am confused is the log pattern in hive and spark are like following
spark/conf/log4j.properties
{code}
log4j.rootCategory=DEBUG, console$
log4j.appender.console=org.apache.log4j.ConsoleAppender$
log4j.appender.console.target=System.err$
log4j.appender.console.layout=org.apache.log4j.PatternLayout$
log4j.appender.console.layout.ConversionPattern=%d{yy/MM/dd HH:mm:ss} %p %t 
%c{1}: %m%n$
{code}

hive/conf/hive-log4j.properties
{code}
appender.console.type = Console$
appender.console.name = console$
appender.console.target = SYSTEM_ERR$
appender.console.layout.type = PatternLayout$
appender.console.layout.pattern = %d{ISO8601} %5p [%t] %c{2}: %m%n$
{code}

thread-name( %t ) is included in the pattern, so current we can see the 
thread-name in the log. Is my understand 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
>         Attachments: executor-driver-log.PNG
>
>
> 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.15#6346)

Reply via email to