This was actually going to be my suggestion. You could create a custom framework/scheduler to handle these types of tasks and configure mesos to give priority to this framework using roles, and weights.
On Thu, Mar 12, 2015 at 1:38 PM, Konrad Scherer < [email protected]> wrote: > On 03/12/2015 04:54 AM, Aaron Carey wrote: > >> Hi All, >> >> In setting up our cluster, we require things like consul to be running on >> all of >> our nodes. I was just wondering if there was any sort of best practice >> (or a >> scheduler perhaps) that people could share for this sort of thing? >> > > I am in a similar situation. I want to start a single "source cache" (over > 200GB) data container on each of my builder nodes. I had the idea of > creating a custom resource on each slave and creating a scheduler to handle > this resource only. Has anyone tried this? The only problem I can see is > that there is no way to prevent another scheduler from taking the offered > custom resource, but since it is custom it seems unlikely. > > I would love to use Marathon for this, but looks like Marathon does not > support custom resources and the issue[1] is in the backlog. Perhaps when > Mesos and Marathon get dynamic resources[2] support? > > [1]: https://github.com/mesosphere/marathon/issues/375 > [2]: https://issues.apache.org/jira/browse/MESOS-2018 > > -- > Konrad Scherer, MTS, Linux Products Group, Wind River >
