You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Nico Kruber (Jira)" <ji...@apache.org> on 2021/08/16 21:43:00 UTC
[jira] [Updated] (FLINK-23812) Support configuration of the RocksDB
info logging via configuration
[ https://issues.apache.org/jira/browse/FLINK-23812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nico Kruber updated FLINK-23812:
--------------------------------
Summary: Support configuration of the RocksDB info logging via configuration (was: Support configuration of the RocksDB logging via configuration)
> Support configuration of the RocksDB info logging via configuration
> -------------------------------------------------------------------
>
> Key: FLINK-23812
> URL: https://issues.apache.org/jira/browse/FLINK-23812
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
> Affects Versions: 1.13.2
> Reporter: Nico Kruber
> Assignee: Nico Kruber
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
>
> Since FLINK-14482 has been merged now, we should also allow users to configure more than just the log level (FLINK-20911) but also the following parameters so that they can safely enable RocksDB logging again (once disabled by default in FLINK-15068) by using a rolling logger, for example:
> - max log file size via {{state.backend.rocksdb.log.max-file-size}}
> - logging files to keep via {{state.backend.rocksdb.log.file-num}}
> - log directory {{state.backend.rocksdb.log.dir}}, e.g. to put these logs onto a (separate) volume that may not be local and is retained after container shutdown for debugging purposes
--
This message was sent by Atlassian Jira
(v8.3.4#803005)