hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sahil Takiar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-13517) Hive logs in Spark Executor and Driver should show thread-id.
Date Wed, 22 Mar 2017 21:30:42 GMT

     [ https://issues.apache.org/jira/browse/HIVE-13517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sahil Takiar updated HIVE-13517:
--------------------------------
    Attachment: HIVE-13517.1.patch

Attaching a pre-lim patch. This basically makes it possible for users to specify the location
of a custom log4j.properties to be used in the HoS driver and executor.

The advantage is that different sessions can now use different log4j configs, rather than
a single log4j config for the entire spark installation.

> 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: Sahil Takiar
>         Attachments: executor-driver-log.PNG, HIVE-13517.1.patch
>
>
> 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)

Mime
View raw message