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

Slot request may not be removed when it has already be assigned in slot manager

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      When task executor report a slotA with allocationId1, it may happen that slot manager record slotA is assigned to allocationId2, and the slot request with allocationId1 is not assigned. Then slot manager will update itself with slotA assigned to allocationId1, by it does not clear the slot request with allocationId1.

      For example:

      1. There is one free slot in slot manager.
      2. Now come two slot request with allocationId1 and allocationId2.
      3. The slot is assigned to allocationId1, but the requestSlot call timeout.
      4. SlotManager assign the slot to allocationId2 and insert a slot request with allocationId1.
      5. The second requestSlot call to task executor return SlotOccupiedException.
      6. SlotManager update the slot to allocationID1, but the slot request is left.

      Attachments

        Activity

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

          People

            tiemsn shuai.xu
            tiemsn shuai.xu
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment