Pass each mesos-slave.sh a unique --work_dir, --hostname, and --port, and
divvy up --resources among them and they'll all run on a single host.
On Tue, Mar 22, 2016 at 10:17 AM, Shiyao Ma wrote:
> Hi,
>
> I vaguely remember last time I asked a question on this lists. Some
> comments mentioned t
So I have a bespoke framework that runs under 1.4.0 using the v1 HTTP API,
custom executor, checkpointing disabled.
When the framework is running happily and a new agent is added to the
cluster all the existing executors immediately get terminated.
The scheduler is told of the lost executors and ta
are with a cluster all on a single host, master
> on 127.0.0.1, agents have their own ip's and hostnames and ports.```
>
> What does this mean? How are all your masters and agents on the same host
> but still get different ips and hostnames?
>
>
> On Tue, Nov 14, 2017
rote:
> How is agent2 able to see agent1's containers? Are they running on the
> same box!? Are they somehow sharing the filesystem? If yes, that's not
> supported.
>
> On Wed, Nov 15, 2017 at 8:07 AM, Dan Leary wrote:
>
>> Sure, master log and agent logs are at
ll of the "containers" we know about based on the
> // existing cgroups.
> Try> cgroups =
> cgroups::get(freezerHierarchy, flags.cgroups_root);
Thanks much.
On Wed, Nov 15, 2017 at 11:37 AM, James Peach wrote:
>
> > On Nov 15, 2017, at 8:24 AM, Dan Leary wro
Wed, Nov 15, 2017 at 11:58 AM, Dan Leary wrote:
>
>> Bingo.
>> It probably doesn't hurt to differentiate --runtime_dir per agent but the
>> real problem is that --cgroups_root needs to be different too.
>> As one might infer from linux_launcher.cpp:
>>
Don't know what the official recommendation is or if there is one.
But what I currently do is deserialize the MasterInfos from zk, then use
the Operator API to attempt a GET_MASTER from each one until I get an
answer.
Relies on the "json.info" constant defined in src/master/constants.hpp and
the fa
Been doing some testing with mesos 1.11.0 and zookeeper's "dynamic
reconfiguration" capability.
https://zookeeper.apache.org/doc/r3.6.3/zookeeperReconfig.html
Seems prima facie like mesos-master can handle a dynamic reconfig of the zk
ensemble up to the point
where a new set of participants has be
>
> Thomas
> --
> *From:* Charles-François Natali
> *Sent:* Wednesday, 9 March 2022 23:44
> *To:* user
> *Subject:* [BULK]Re: Mesos and Zookeeper Dynamic Reconfiguration?
>
> Hi Dan,
>
> I don't think anyone h
ature and Mesos is
> not aware of those changes.
>
> Bw,
>
> Thomas
> --
> *From:* Dan Leary
> *Sent:* Thursday, 10 March 2022 16:16
> *To:* user@mesos.apache.org
> *Subject:* [BULK]Re: [BULK]Re: Mesos and Zookeeper Dynamic
> Reconfigura
We're using mesos 1.11 straight out of the box on ubuntu 18.04 at touchplan.io
running our own bespoke framework. Would like to get it to ubuntu 22.04. We
have limited resources to commit to mesos development, but it's not totally out
of the question.
-Dan
Fr
11 matches
Mail list logo
