You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yun Tang (Jira)" <ji...@apache.org> on 2021/01/15 03:37:00 UTC
[jira] [Commented] (FLINK-20911) Support configuration of RocksDB
log level
[ https://issues.apache.org/jira/browse/FLINK-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17265661#comment-17265661 ]
Yun Tang commented on FLINK-20911:
----------------------------------
merged in master 02a79dec5aa2d1aaf9c7acb5d59da57fefe8ead3
> Support configuration of 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
> Assignee: fanrui
> Priority: Major
> Labels: pull-request-available
>
> 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)