You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/09/01 22:38:00 UTC
[jira] [Updated] (FLINK-22234) Read savepoint before creating
ExecutionGraph
[ https://issues.apache.org/jira/browse/FLINK-22234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-22234:
-----------------------------------
Labels: auto-deprioritized-major pull-request-available (was: pull-request-available stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion.
> Read savepoint before creating ExecutionGraph
> ---------------------------------------------
>
> Key: FLINK-22234
> URL: https://issues.apache.org/jira/browse/FLINK-22234
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Chesnay Schepler
> Priority: Minor
> Labels: auto-deprioritized-major, pull-request-available
>
> Savepoints are currently read when the ExecutionGraph is created.
> This is causing problems when determining the (max) parallelism the job is run with, because the savepoint may impose additional restrictions.
> This caused quite a few headaches in FLINK-21844, and further requires the execution vertices to have a mutable max parallelism.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)