[
https://issues.apache.org/jira/browse/FLINK-21688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17311244#comment-17311244
]
xiaogang zhou commented on FLINK-21688:
---------------------------------------
[~yunta] Thx for explanation, will try to send mail to user-mailing list first
in the future.
As I mentioned above, when restore with rescaling, the "high thread " of the
rocksdb is always can slow down the iteration process. because the
setIncreaseParallelism set the thread number to 1. Do we need to do some work
on it?
> 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)
