[VOTE] Release Apache Mesos 1.2.3 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.2.3. 1.2.3 is our last scheduled bug fix release in the 1.2.x branch. The CHANGELOG for the release is available at: https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.2.3-rc1

Stripping Offer.AllocationInfo and Resource.AllocationInfo for non-MULTI_ROLE schedulers.

Hi folks, When we released MULTI_ROLE support, Offers and Resources within them included additional information, specifically the AllocationInfo which indicated which role was being allocated to: https://github.com/apache/mesos/blob/1.3.0/include/ mesos/v1/mesos.proto#L907-L923

Re: Adding a new agent terminates existing executors?

Understood. Thanks for the help. On Wed, Nov 15, 2017 at 3:04 PM, Vinod Kone wrote: > Yes, there are a bunch of flags that need to be different. There are > likely some isolators which will not work correctly when you have multiple > agents on the same host even then. The

[RESULT][VOTE] Release Apache Mesos 1.4.1 (rc1)

Hi all, The vote for Mesos 1.4.1 (rc1) has passed with the following votes. +1 (Binding) -- *** Vinod Kone *** Kapil Arya *** Anand Mazumdar There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.4.1 It is

Re: Adding a new agent terminates existing executors?

Yes, there are a bunch of flags that need to be different. There are likely some isolators which will not work correctly when you have multiple agents on the same host even then. The garbage collector assumes it has sole access to the disk containing work dir etc etc. In general, running multiple

Re: Adding a new agent terminates existing executors?

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: Future LinuxLauncherProcess::recover( > const list& states) > { > // Recover all of the

Re: Adding a new agent terminates existing executors?

> On Nov 15, 2017, at 8:24 AM, Dan Leary wrote: > > Yes, as I said at the outset, the agents are on the same host, with different > ip's and hostname's and work_dir's. > If having separate work_dirs is not sufficient to keep containers separated > by agent, what

Re: Adding a new agent terminates existing executors?

Yes, as I said at the outset, the agents are on the same host, with different ip's and hostname's and work_dir's. If having separate work_dirs is not sufficient to keep containers separated by agent, what additionally is required? On Wed, Nov 15, 2017 at 11:13 AM, Vinod Kone

Re: Adding a new agent terminates existing executors?

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 attached. > > Synopsis: In the