[
https://issues.apache.org/jira/browse/FLINK-15747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046395#comment-17046395
]
Nico Kruber commented on FLINK-15747:
-------------------------------------
Yes, for those scenarios, it may make sense to simplify things. I was just
cautious of adding more and more config settings which may confuse users.
If you go down that path, please also have other related log settings in mind.
For the current version of RocksDB we are using, I have the following in my
mind*:
{code}
org.rocksdb.DBOptions#setLogger(org.rocksdb.Logger)
org.rocksdb.DBOptions#setDbLogDir(java.lang.String)
{code}
* Please mind that things like file size and number of files for the rolling
logger currently do not work - see
https://github.com/dataArtisans/frocksdb/pull/12
> Enable setting RocksDB log level from configuration
> ---------------------------------------------------
>
> Key: FLINK-15747
> URL: https://issues.apache.org/jira/browse/FLINK-15747
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
> Reporter: Yu Li
> Assignee: Congxian Qiu(klion26)
> Priority: Major
> Fix For: 1.11.0
>
>
> Currently to open the RocksDB local log, one has to create a customized
> {{OptionsFactory}}, which is not quite convenient. This JIRA proposes to
> enable setting it from configuration in flink-conf.yaml.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
