[
https://issues.apache.org/jira/browse/FLINK-31406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704978#comment-17704978
]
Gyula Fora commented on FLINK-31406:
------------------------------------
This should also apply to regular restarts / redeployments done using the
last-state mechanism such as deployment recovery, unhealthy job restart etc.
> Do not delete jobgraph on scale only last-state upgrades
> --------------------------------------------------------
>
> Key: FLINK-31406
> URL: https://issues.apache.org/jira/browse/FLINK-31406
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Priority: Major
>
> Currently the operator always deletes the jobgraph from HA metadata so that
> it's regenerated for last-state upgrades.
> This is unnecessary for scale only operations. Keeping the jobgraph can
> greately speed up startup time for some jobs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
