Re: Support deadline for tasks

> On Mar 22, 2018, at 10:06 AM, Zhitao Li wrote: > > In our environment, we run a lot of batch jobs, some of which have tight > timeline. If any tasks in the job runs longer than x hours, it does not make > sense to run it anymore. > > For instance, a team would submit a job which builds a

Re: Communicate with a container while using Mesos unified container runtime

On 2018/03/22 23:16:06, Gilbert Song wrote: > Hi Karan, > > It does not seem to me that launching more mesos containers would add more > overheads. > > If you want to achieve *docker exec* for debugging purpose, Mesos supports > that (not in Mesos CLI yet /cc Armand and Kevin), but you could

Re: Communicate with a container while using Mesos unified container runtime

Hi Karan, It does not seem to me that launching more mesos containers would add more overheads. If you want to achieve *docker exec* for debugging purpose, Mesos supports that (not in Mesos CLI yet /cc Armand and Kevin), but you could still rely on dc/os CLI

Mesos scalability

Hi All, I had the following questions: 1. I was wondering if it is possible to have multiple Mesos masters as elected masters in a Mesos cluster so that the load can be balanced amongst the masters. Is there a way to achieve this? In general, can there be a load balancer for the Mesos masters?

Re: Mesos on OS X

Thanks all, that sounds promising! We'll probably give it a go and see how that works out... On Wed, Mar 21, 2018 at 9:32 PM, Jie Yu wrote: > There's no isolation between containers on OSX. Process management is > based on posix process tree (unlike cgroups on Linux), which has some > limitation

Support deadline for tasks

In our environment, we run a lot of batch jobs, some of which have tight timeline. If any tasks in the job runs longer than x hours, it does not make sense to run it anymore. For instance, a team would submit a job which builds a weekly index and repeats every Monday. If the job does not finish be