[ https://issues.apache.org/jira/browse/FLINK-31406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-31406: ----------------------------------- Labels: pull-request-available stale-assigned (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 issue is assigned but has not received an update in 30 days, so it has been labeled "stale-assigned". If you are still working on the issue, please remove the label and add a comment updating the community on your progress. If this issue is waiting on feedback, please consider this a reminder to the committer/reviewer. Flink is a very active project, and so we appreciate your patience. If you are no longer working on the issue, please unassign yourself so someone else may work on it. > 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 > Assignee: Nicholas Jiang > Priority: Major > Labels: pull-request-available, stale-assigned > > 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)