You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "László Bodor (Jira)" <ji...@apache.org> on 2021/05/12 12:41:00 UTC
[jira] [Updated] (HIVE-25107) Thread classpath logging should be
optional
[ https://issues.apache.org/jira/browse/HIVE-25107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
László Bodor updated HIVE-25107:
--------------------------------
Description:
This is since HIVE-21584
I have a *72M* llap executor log file, then I grepped for only "thread class path", piped into a separate file and a result was a *22M* file...1/3-1/4 of the file was classpath info which is not usable for most of the time. This overwhelming amount of classpath info is not needed, assuming that classpath issues are reproducible with more or less effort, user should be responsible for turning on this expensive logging on demand.
> Thread classpath logging should be optional
> -------------------------------------------
>
> Key: HIVE-25107
> URL: https://issues.apache.org/jira/browse/HIVE-25107
> Project: Hive
> Issue Type: Improvement
> Reporter: László Bodor
> Priority: Major
>
> This is since HIVE-21584
> I have a *72M* llap executor log file, then I grepped for only "thread class path", piped into a separate file and a result was a *22M* file...1/3-1/4 of the file was classpath info which is not usable for most of the time. This overwhelming amount of classpath info is not needed, assuming that classpath issues are reproducible with more or less effort, user should be responsible for turning on this expensive logging on demand.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)