[
https://issues.apache.org/jira/browse/FLINK-22234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-22234:
-----------------------------------
Labels: pull-request-available stale-major (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Major
> Labels: pull-request-available, stale-major
>
> 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)
