[
https://issues.apache.org/jira/browse/FLINK-19011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327682#comment-17327682
]
Flink Jira Bot commented on FLINK-19011:
----------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Parallelize the restore operation in OperatorStateBackend
> ----------------------------------------------------------
>
> Key: FLINK-19011
> URL: https://issues.apache.org/jira/browse/FLINK-19011
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Checkpointing
> Affects Versions: 1.11.1
> Reporter: Jiayi Liao
> Priority: Major
> Labels: stale-major
>
> To restore the states, union state needs to read state handles produced by
> all operators. And currently during the restore operation, Flink iterates the
> state handles one by one, which could last tens of minutes if the magnitude
> of state handles exceeds ten thousand.
> To accelerate the process, I propose to parallelize the random reads on HDFS
> and deserialization. We can create a runnable for each state handle and let
> it return the metadata and deserialized data, which can be aggregated in main
> thread.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
