[FLINK-26583] The user is not informed in any way when a job is resubmitted but already globally-terminated

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.15.0
• Fix Version/s: 1.15.0
• Component/s: Runtime / Coordination
• Labels: pull-request-available
• Assignee: Matthias Pohl
• Reporter: Matthias Pohl
• Created: 10/Mar/22 12:00
• Updated: 14/Mar/22 09:50
• Resolved: 11/Mar/22 17:02

Description

-We experience some unwanted behavior if a clean JobResult is listed in the JobResultStore and a job with the same Job ID is submitted in Application Mode.
We would expect that the second submission fails with a DuplicateJobSubmissionException. Instead, the submission succeeds with the job not running anymore.-

Update:
We reiterated over the problem and decided that the Exception is not the desired failure because it would cause a failover in k8s setups, for instance. We rather want to inform the user through a warning because Flink still behaves as expected.

Issue Links

• Discovered while testing: FLINK-26391 Release Testing: Application Mode recovery does not re-trigger a job which failed during cleanup (FLINK-11813)
• is caused by: FLINK-25430 Introduce JobResultStore
• links to: GitHub Pull Request #19047