Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-14106 Make SlotManager pluggable
  3. FLINK-16442

Make MesosResourceManager starts workers using WorkerResourceSpec requested by SlotManager

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Won't Do
    • None
    • None
    • Deployment / Mesos
    • None

    Description

      This means MesosResourceManager no longer:

      • be aware of the default task executor resources
      • assumes all workers are identical

      TBH, I'm not sure how many use cases do we have that needs to bring a different slot allocation strategy to the Mesos deployment. I think we can discuss whether we want to do this step or not.

      Attachments

        Activity

          People

            Unassigned Unassigned
            xtsong Xintong Song
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: