Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-5197

Late JobStatusChanged messages can interfere with running jobs

Agile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersStop watchingWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 1.1.3, 1.2.0
    • 1.1.4, 1.2.0
    • Runtime / Coordination
    • None

    Description

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            trohrmann Till Rohrmann
            trohrmann Till Rohrmann
            Votes:
            0 Vote for this issue
            Watchers:
            2 Stop watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment