[
https://issues.apache.org/jira/browse/FLINK-26916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514573#comment-17514573
]
David Morávek commented on FLINK-26916:
---------------------------------------
As long as the operator has access to user credentials (s3), can you simply get
the latest checkpoint directly from the filesystem?
> I am afraid I cannot agree with you about that clusterId shouldn't be reused.
> Users just need to do the manual clean-up for job result store if they want
> to reuse the same cluster-id.
Having a clean entry in JRS implies that all cluster resources (including HA)
have been cleaned up (this is not what happens here). Then yes, the id should
be safe to reuse after cleaning up the entry.
> The Operator ignores job related changes (jar, parallelism) during last-state
> upgrades
> --------------------------------------------------------------------------------------
>
> Key: FLINK-26916
> URL: https://issues.apache.org/jira/browse/FLINK-26916
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-0.1.0, kubernetes-operator-1.0.0
> Reporter: Matyas Orhidi
> Assignee: Yang Wang
> Priority: Blocker
> Labels: pull-request-available
> Fix For: kubernetes-operator-0.1.0
>
>
> RC: The old jobgraph is being reused when resuming
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
