[ https://issues.apache.org/jira/browse/FLINK-21688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17307520#comment-17307520 ]
xiaogang zhou commented on FLINK-21688: --------------------------------------- [~yunta] Hello, Can you please help understand why using the setIncreaseParallelism to set the rocksdb thread number, but not use the setMaxBackgroundJobs. the setIncreaseParallelism will limit the flush thread to 1 in the whole process. why we have to limit it? thx a lot if you let me know your thinking. > we use setIncreaseParallelism function, can cause slow flush in restore > ----------------------------------------------------------------------- > > Key: FLINK-21688 > URL: https://issues.apache.org/jira/browse/FLINK-21688 > Project: Flink > Issue Type: Improvement > Components: Runtime / State Backends > Affects Versions: 1.11.3 > Reporter: xiaogang zhou > Priority: Major > > we use setIncreaseParallelism function, can cause slow flush in restore > rescaling case. As this function limits the HIGH threads to 1. > > Why not set the MAX jobs to 40, which will offer more flush thread to enable > a fast recovery -- This message was sent by Atlassian Jira (v8.3.4#803005)