You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Grégoire Seux <g....@criteo.com> on 2019/10/07 17:19:02 UTC
Re: [BULK]Re: large task scheduling on multi-framework cluster
Hello Benjamin,
> Note that with the newest marathon that is capable of handling multiple roles, you would not need to run a dedicated marathon instance.
True it is not strictly necessary. We use this as an easy way to deal with various needs:
- quota on some roles (a multi role marathon could address this)
- easy authorization configuration (otherwise we would need to configure authorizations to only allow specific users to use some roles)
- general resiliency: if one marathon has a random bug and start deleting all its apps, at least the others are unlikely to do this at the same time!
- performance: each marathon handle less tasks and less healthchecks
But it is not really the topic of my question, I gave this as a context precision.
Anyone encounting the same issue when scheduling large tasks?
--
Grégoire
Re: [BULK]Re: large task scheduling on multi-framework cluster
Posted by Tim Harper <ti...@gmail.com>.
Marathon 1.9 has multirole support, by the way
Sent from my Apple Watch
On Oct 7, 2019, at 11:19, Grégoire Seux <g....@criteo.com> wrote:
> Hello Benjamin,
>
>> Note that with the newest marathon that is capable of handling multiple roles, you would not need to run a dedicated marathon instance.
> True it is not strictly necessary. We use this as an easy way to deal with various needs:
> - quota on some roles (a multi role marathon could address this)
> - easy authorization configuration (otherwise we would need to configure authorizations to only allow specific users to use some roles)
> - general resiliency: if one marathon has a random bug and start deleting all its apps, at least the others are unlikely to do this at the same time!
> - performance: each marathon handle less tasks and less healthchecks
>
> But it is not really the topic of my question, I gave this as a context precision.
>
> Anyone encounting the same issue when scheduling large tasks?
>
> --
> Grégoire
>
>
>