[
https://issues.apache.org/jira/browse/FLINK-23812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nico Kruber closed FLINK-23812.
-------------------------------
Fix Version/s: 1.14.0
Release Note: With RocksDB bumped to 6.20.3 (FLINK-14482), you can now
also configure a rolling info logging strategy by configuring it accordingly
via newly added state.backend.rocksdb.log.* settings. This can be helpful for
debugging RocksDB (performance) issues in containerized environments where the
local data dir is volatile but the logs should be retained on a separate volume
mount.
Resolution: Fixed
Merged on master via a86f8a5f59fbc49fb62feeda26c159a716631752
> Support configuration of the RocksDB 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)
