recovery_agent_removal_limit usage question?

toady i have a curious to read mesos source code for --recovery_agent_removal_limit. how does it working from source code. i have not found any useful logic for recovery_agent_removal_limit. anyone can do me favor? -- Deshi Xiao Twitter: xds2000 E-mail: xiaods(AT)gmail.com

Re: Questions about the mesos protocol

Docker volume support in Mesos Containerizer, reference http://mesos.apache.org/documentation/latest/docker-volume/ > 在 2017年8月31日，下午3:11，yawei@xtaotech.com 写道： > > Hi all >In current mesos protocol(defined in

回复: Questions about the mesos protocol

Hi all 1. If we add a third SLAVE mode for Volume Mode in mesos.proto, will it result in not working for all of frameworks? For example, Volume Mode is enumerate type in mesos.proto, we want to add a third SLAVE mode and modify marathon to support DockerContainerizer, This SLAVE

Re: Questions about the mesos protocol

On 2017-08-31 22:46, Jie Yu wrote: > Sorry, the comment above applies to MesosContainerizer. For> > DockerContainerizer, all mounts will be private (docker default). We don't> > have immediate plan to support slave/shared mount for DockerContainerizer.> > You can use MesosContainerizer to

RE: [Proposal] Use jemalloc as default memory allocator for Mesos

There's a jemalloc-cmake repo that has cmake support (I just tested it, and works great with VS 2017 x64). You can find it here: https://github.com/jemalloc/jemalloc-cmake However, it looks like it's a few versions behind the main jemalloc repo (4.3.1 looks to be the latest version in the

Re: [Proposal] Use jemalloc as default memory allocator for Mesos

I looked at the Windows build a bit closer, and the Cygwin requirement appears to simply be for the use of autogen to generate headers. Once the headers are generated, the rest of the build is driven by a committed Visual Studio 2015 solution, which means that jemalloc can be built natively on

[RESULT][VOTE] Release Apache Mesos 1.1.3 (rc2)

Hi all, The vote for Mesos 1.1.3 (rc2) has passed with the following votes. +1 (Binding) -- Alex R Till Tönshoff Vinod Kone There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.1.3 It is recommended to use a

RE: [Proposal] Use jemalloc as default memory allocator for Mesos

The fact that Firefox works with jemalloc isn't necessarily indicative. I, for one, would like to avoid dependencies on Cygwin for Mesos. We don't need it today, and we're building an awful lot. (Interesting that you brought up SASL-based auth - that's currently in the process of being ported

Re: Questions about the mesos protocol

Sorry, the comment above applies to MesosContainerizer. For DockerContainerizer, all mounts will be private (docker default). We don't have immediate plan to support slave/shared mount for DockerContainerizer. You can use MesosContainerizer to launch Docker containers, see doc here:

Re: [VOTE] Release Apache Mesos 1.1.3 (rc2)

+1 Tested on internal CI and additionally `make check` on Fedora 25 and Mac OS 10.11.6. On Thu, Aug 31, 2017 at 2:50 AM, Till Toenshoff wrote: > +1 > > Tested on internal CI as well as on macOS 10.12 and macOS 10.13 DP 8 using > Apple’s clang (Xcode 8.3.3 and Xcode 9.0.0 beta

Re: Questions about the mesos protocol

By default, all host volumes are slave mounts. We're planning to add support for allowing a host volume to be a shared mount. - Jie On Thu, Aug 31, 2017 at 12:11 AM, yawei@xtaotech.com < yawei@xtaotech.com> wrote: > Hi all > In current mesos protocol(defined in mesos.proto), the

Questions about the mesos protocol

Hi all In current mesos protocol(defined in mesos.proto), the volume mode can only be set to RO or RW. How can I luanch a docker with a volume in Slave mode via Mesos? Best wishes! yawei@xtaotech.com