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

Make SlotManager pluggable

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

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.9.0
    • Fix Version/s: 1.13.0
    • Component/s: Runtime / Coordination
    • Labels:
      None

      Description

      As we are enabling fine grained resource management in 1.10, we can have various resource scheduling strategies. Such strategies generally should make the following three decisions.

      • When to launch new / release existing TMs? (How many TMs)
      • What and how many resources should TMs be started with?
      • How to allocate between slot requests and TM resources?

      We may want to make above decisions differently in different scenarios (active/reactive mode, perjob/session mode, etc.). Therefore, we propose to make the scheduling strategies pluggable.

      We propose to make the following changes:

      • Make SlotManager an interface, and implements it differently for different strategies strategies.
      • Modify ResourceManager-SlotManager interfaces to cover all the three decisions mentioned above in SlotManager. In particular,┬áSlotManager needs to allocate TM resources instead of slot resources from ResourceActions.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              xintongsong Xintong Song
              Reporter:
              xintongsong Xintong Song

              Dates

              • Created:
                Updated:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 50m
                50m

                  Issue deployment