mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomek Janiszewski <jani...@gmail.com>
Subject Re: mesos-execute cmd
Date Wed, 20 Jun 2018 14:15:48 GMT
IMO it requires a custom framework that will handle spiting task into
multiple nodes. I need more details to help.

śr., 20 cze 2018 o 15:38 użytkownik Abel Souza <abel@cs.umu.se> napisał:

> Anyone that could suggest me anything? Is it a problem that could be fixed
> by writing a custom framework?
>
> /Abel
>
> On 06/13/2018 06:05 AM, Abel Souza wrote:
>
> Did you mean through ‘mesos-execute’ command or is it a Mesos general
> behavior?
>
> Best,
>
> /Abel Souza
>
> On Jun 13, 2018, at 02:04, Qian Zhang <zhq527725@gmail.com> wrote:
>
> It is possible to use multiple offers from a single agent node to launch a
> task, but I do not think you can use multiple offers from different agent
> nodes to launch a task.
>
>
> Regards,
> Qian Zhang
>
> On Tue, Jun 12, 2018 at 9:12 PM, Abel Souza <abel@cs.umu.se> wrote:
>
>> Hello,
>>
>> I believe this question relates to the framework used by the
>> mesos-execute command (available by default in Mesos installation):
>>
>> When I request a number of cores greater than what is available in one
>> single node, the mesos-execute automatically turn down all offers made
>> by Mesos and hangs forever. E.g.: Each agent node in my cluster has 8
>> cores, and when I request 9 cores through mesos-execute
>> --resources='cpus:9', the command waits forever. But If I execute mesos-execute
>> --resources='cpus:8', tasks start execution right away.
>>
>> So I would like to know if there is a way to enable the mesos-execute to
>> handle situations where multiple nodes are needed to satisfy a resource
>> request. If so, what would be needed?
>>
>> Thank you,
>>
>> /Abel Souza
>>
>
>
>

Mime
View raw message