[
https://issues.apache.org/jira/browse/FLINK-25974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Pohl resolved FLINK-25974.
-----------------------------------
Fix Version/s: 1.15.0
Resolution: Fixed
master:
17c89564ae3
e8a91fd8428
> Make cancellation of jobs depend on the JobResultStore
> ------------------------------------------------------
>
> Key: FLINK-25974
> URL: https://issues.apache.org/jira/browse/FLINK-25974
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.15.0
> Reporter: Matthias Pohl
> Assignee: Matthias Pohl
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {{JobManagerRunner}} instances were cancellable as long as the instance was
> still registered in the {{Dispatcher.jobManagerRunnerRegistry}}. With the
> cleanup being done concurrently (i.e. not relying on the
> {{JobManagerRunnerRegistry}} to be cleaned up anymore), the cancellation of a
> job should only be possible as long as the job is not globally finished and
> before cleanup is triggered.
> We should verify whether a job is listed in the {{JobResultStore}} and only
> enable the user to cancel the job if that's not the case.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
