[
https://issues.apache.org/jira/browse/FLINK-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-5197.
--------------------------------
Resolution: Fixed
1.2.0 fixed via ae0975c16b997fe792790216820a559d01a01894
1.1.4 fixed via 569a9666fca9d9113d9fc7f0382faf986afb036f
> Late JobStatusChanged messages can interfere with running jobs
> --------------------------------------------------------------
>
> Key: FLINK-5197
> URL: https://issues.apache.org/jira/browse/FLINK-5197
> Project: Flink
> Issue Type: Bug
> Components: JobManager
> Affects Versions: 1.2.0, 1.1.3
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Minor
> Fix For: 1.2.0, 1.1.4
>
>
> When the {{JobManager}} receives a {{JobStatusChanged}} message, it will look
> up the {{ExecutionGraph}} for the given {{JobID}}. If there is no
> {{ExecutionGraph}}, then a {{RemoveJob}} message is sent to itself. In the
> general case, this is not problematic, because the {{RemoveJob}} message
> won't do anything if there is no {{ExecutionGraph}}. However, since this is
> an asynchronous call, it can happen that the corresponding job of the
> {{JobID}} is recovered before receiving the {{RemoveJob}} message. In this
> case, the newly recovered job would be removed.
> I propose to change the behaviour such that a {{JobStatusChanged}} for a
> non-existing {{ExecutionGraph}} will be simply ignored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
