You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Riza Suminto (Jira)" <ji...@apache.org> on 2021/11/02 19:33:00 UTC

[jira] [Commented] (IMPALA-5256) ERROR log files can get very large

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

Riza Suminto commented on IMPALA-5256:
--------------------------------------

We can force glog to roll all log files by calling google::SetLogFilenameExtension() to some random ext and immediately set it back to empty extension.
[https://github.com/google/glog/blob/c27c3a8/src/logging.cc#L976-L987]

I've tried this solution, combined with stdout/stderr reattachment and checking the log file size periodically with boost::filesystem::file_size(), and it seems to work well.

> ERROR log files can get very large
> ----------------------------------
>
>                 Key: IMPALA-5256
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5256
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 2.5.5.
>            Reporter: Mala Chikka Kempanna
>            Assignee: Riza Suminto
>            Priority: Major
>              Labels: supportability
>
> There's a user who's reporting seeing very large ERROR log files (up to 7gb) that don't seem to be obeying the --max_log_size parameter.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org