You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mesos.apache.org by "Niklas Quarfot Nielsen (JIRA)" <ji...@apache.org> on 2014/05/10 23:56:38 UTC

[jira] [Created] (MESOS-1334) Workflow for gang scheduling frameworks

Niklas Quarfot Nielsen created MESOS-1334:
---------------------------------------------

             Summary: Workflow for gang scheduling frameworks
                 Key: MESOS-1334
                 URL: https://issues.apache.org/jira/browse/MESOS-1334
             Project: Mesos
          Issue Type: Bug
            Reporter: Niklas Quarfot Nielsen


Today, schedulers need to know up-front what to run on an offer. This doesn't fit well with gang scheduling where multiple resources are reserved and the launch mechanism not known up front.

With a couple of primitives already in the pipeline, this should be possible by:
- Being able to run an empty job which is marked as TASK_IDLE. Together with preemptable resources, the idle resource can be used in the interim.
- When all resources have been acquired, use replace task to launch gang scheduled job.

I'd love to hear some input on gang scheduling, if this would be sufficient and if you have other ideas on how to address this issue.



--
This message was sent by Atlassian JIRA
(v6.2#6252)