[
https://issues.apache.org/jira/browse/HIVE-15631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255957#comment-16255957
]
Prasanth Jayachandran commented on HIVE-15631:
----------------------------------------------
I would actually recommend setting sessionId in MDC context (and cleanup when
session is closed). With MDC, sessionId can be included in the pattern layout
use {X} option or the MDC key. Also adding it to MDC has benefit of using
routing appender to redirect log lines corresponding to a specific session to
its own files. MDC is used by operation logging and LLAP to redirect
query/session specific log lines to separate files. We could use that for
hive.log as well.
> Optimize for hive client logs , you can filter the log for each session
> itself.
> -------------------------------------------------------------------------------
>
> Key: HIVE-15631
> URL: https://issues.apache.org/jira/browse/HIVE-15631
> Project: Hive
> Issue Type: Improvement
> Components: CLI, Clients, Hive
> Reporter: tartarus
> Assignee: tartarus
> Attachments: HIVE_15631.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> We have several hadoop cluster, about 15 thousand nodes. Every day we use
> hive to submit above 100 thousand jobs.
> So we have a large file of hive logs on every client host every day, but i
> don not know the logs of my session submitted was which line.
> So i hope to print the hive.session.id on every line of logs, and then i
> could use grep to find the logs of my session submitted.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
