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/17 10:57:01 UTC

[jira] [Commented] (HIVE-25107) Classpath logging should be on DEBUG level

    [ https://issues.apache.org/jira/browse/HIVE-25107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17346072#comment-17346072 ] 

László Bodor commented on HIVE-25107:
-------------------------------------

PR merged, thanks for the inputs [~pgaref], [~zmatyus]!

> Classpath logging should be on DEBUG level
> ------------------------------------------
>
>                 Key: HIVE-25107
>                 URL: https://issues.apache.org/jira/browse/HIVE-25107
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: László Bodor
>            Assignee: László Bodor
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 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. Not to mention performance implications which cannot be ignored beyond a certain amount of log messages.
> https://github.com/apache/hive/commit/a234475faa2cab2606f2a74eb9ca071f006998e2#diff-44b2ff3a3c4a6cfcaed0fcb40b74031844f8586e40a6f8261637e5ebcd558b73R4577



--
This message was sent by Atlassian Jira
(v8.3.4#803005)