[jira] [Commented] (FLINK-20911) Support to modify RocksDB LOG level

["Yun Tang (Jira)" <ji...@apache.org>]

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

Yun Tang commented on FLINK-20911:
----------------------------------

I think the log level should be configurable and we could add warnings within related option to tell users set other level carefully.

Do you like to take this ticket [~fanrui] ?

> Support to modify RocksDB LOG level
> -----------------------------------
>
>                 Key: FLINK-20911
>                 URL: https://issues.apache.org/jira/browse/FLINK-20911
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / State Backends
>    Affects Versions: 1.13.0, 1.12.1
>            Reporter: fanrui
>            Priority: Major
>
> The LOG level of RocksDB is hard-coded and is always HEADER_LEVEL. Sometimes RocksDB becomes unstable due to unreasonable parameter settings, and the problem can be reproduced after restart. At this time, you may need to check some LOGs to troubleshoot.
> It may be better if the LOG level of RocksDB can be adjusted. Of course, the default LOG level is still HEADER_LEVEL. When dealing with problems, it can be adjusted to DEBUG_LEVEL.



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