[
https://issues.apache.org/jira/browse/KUDU-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337543#comment-17337543
]
ASF subversion and git services commented on KUDU-2754:
-------------------------------------------------------
Commit 00c1b674545541a8a2a17aaca0738136540eb8b8 in kudu's branch
refs/heads/master from Grant Henke
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=00c1b67 ]
KUDU-2754: Mark max_log_files as stable
The max_log_files feature has existed and been in use since 2016.
This patch marks the flag as stable so it can be used without
the need of unlocking experimental flags.
Change-Id: Icd8ca1ce314cc0d333c57a6582165da475224afb
Reviewed-on: http://gerrit.cloudera.org:8080/17362
Tested-by: Kudu Jenkins
Reviewed-by: Grant Henke <granthe...@apache.org>
> Keep a maximum number of old log files
> --------------------------------------
>
> Key: KUDU-2754
> URL: https://issues.apache.org/jira/browse/KUDU-2754
> Project: Kudu
> Issue Type: Improvement
> Reporter: Grant Henke
> Assignee: Grant Henke
> Priority: Major
> Labels: beginner, trivial
>
> Kudu generates various different log files
> (INFO,WARNING,ERROR,diagnostic,minidumps,etc). To prevent issues running out
> of logging space, it would be nice if a user could configure the maximum
> number of each log file type to keep.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
