[
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 auto-deprioritized-minor
pull-request-available (was: auto-deprioritized-major pull-request-available
stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> 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.20.10#820010)
