[
https://issues.apache.org/jira/browse/HIVE-16005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879381#comment-15879381
]
Siddharth Seth commented on HIVE-16005:
---------------------------------------
Is there a utility method to construct queryName":"dagIndex ? I can use that,
or the one used in the log files. End goal is not to have free flowing text -
which is what dagName was.
bq. 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.
This is to have the thread name in the trace.
bq. Also in constructThreadNameSuffix, why does it have to do the dance with
all the IDs, aren't all of them appended if you just do attemptId toString?
Cutting down the length, since it will be logged on each line.
> 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)
