[
https://issues.apache.org/jira/browse/HIVE-16005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877707#comment-15877707
]
Prasanth Jayachandran commented on HIVE-16005:
----------------------------------------------
for constructUniqueQueryId.. can we use the same format as that of filenames
generated by query-routing logger? (queryId-dagId) This way easier to locate
the corresponding log file.
Appending suffix to the thread name, is it primarily to get some context from
jstack output? For stacktraces that gets logged will already have these info
via NDC.
> miscellaneous small fixes to help with llap debuggability
> ---------------------------------------------------------
>
> Key: HIVE-16005
> URL: https://issues.apache.org/jira/browse/HIVE-16005
> Project: Hive
> Issue Type: Task
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: HIVE-16005.01.patch
>
>
> - Include proc_<processname> in cli, beeline, metastore, hs2 process args
> - LLAP history logger - log QueryId instead of dagName (dag name is free
> flowing text)
> - LLAP JXM ExecutorStatus - Log QueryId instead of dagName. Sort by running /
> queued
> - Include thread name in TaskRunnerCallable so that it shows up in stack
> traces (will cause extra output in logs)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
