Re: Re: Next steps for Mesos

Hello, Criteo is still an active user of Mesos, running it worldwide for most of its production workloads. We currently run a fork of Mesos 1.9.x (with some patches that were not upstreamed but not that much), and we don't plan to upgrade to the latest version for now. We will continue to

RE: Re:

Hi, I too would be interested in this group. In real world, it does makes sense to have best practices around operations. Regards, Sundeep Kumar From: Armand Grillet Sent: Tuesday, July 10, 2018 11:51 AM To: user@mesos.apache.org Subject: Re: I would be interested. Le mar. 10 juil. 2018 à

Re: RE: Struggling with running Docker container on Windows agent

Awesome to hear it! On 02/05/2018 3:30 pm, ajkf9uvxc ajkf9uvxc wrote: > After compiling the tip of master from 2018-02-02 on Windows and then doing > the exact same steps as before IT WORKS NOW ! docker ps shows the started > container. (In this case the network setting is "networks": [ {

Re: RE: Struggling with running Docker container on Windows agent

After compiling the tip of master from 2018-02-02 on Windows and then doing the exact same steps as before IT WORKS NOW ! docker ps shows the started container. (In this case the network setting is  "networks": [ { "mode": "container/bridge" } ]  )  Thanks a lot everybody for your help!

Re: Re: make check crashes

Hi Alexander, this is a really good point! My locale is a mix between the US and DE locale: $ locale LANG=en_US.UTF-8 LANGUAGE=en_US LC_CTYPE="en_US.UTF-8" LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE="en_US.UTF-8" LC_MONETARY=de_DE.UTF-8 LC_MESSAGES="en_US.UTF-8" LC_PAPER=de_DE.UTF-8

Re: Re: Cluster history wiped after master leader reelection

Hi thanks for your answer. Too bad the cluster history is wiped out. Is this behavior by design (history is stored on current leader, and cannot be copied by new leader)? Any suggestions for a way of persisting it? Maybe outside of mesos using some data collection?

Re: Re: Mesos 0.25 not incresing Staged/Started counters in the UI

Non-terminal states are gauges (instantaneous measurements) whereas the terminal states are counters (always increasing, at least for the lifetime of a master process). Hopefully this image doesn't get stripped, but we improved the wording here to clarify which are gauges and which are counters:

Re: Re: Mesos 0.25 not incresing Staged/Started counters in the UI

>My point is there is no straightforward way of telling how many tasks had been running on the cluster since it is up. Or am i missing something? I think we could get it from sum up "master/task_*" metrics? On Wed, Feb 24, 2016 at 9:04 PM, Geoffroy Jabouley < geoffroy.jabou...@gmail.com> wrote:

Re: Re: Mesos 0.25 not incresing Staged/Started counters in the UI

Thanks for the clarification. Does staged means "currently in staging state"? In previous versions of Mesos (at least 0.22.1), the Staged value was increased for each staged tasks, to you could tell "X tasks have been executed on the cluster". My point is there is no straightforward way of

Re: Re: external storage with dvdi module

Cool! 2015-11-19 6:30 GMT+08:00 Wong, Steven : > Regarding inquiry by Marica Antonacci on Wed, 18 Nov 2015 04:43:47 -0800 > > Failover scenarios are anticipated in the DVDI module and are being > tracked as this issue on github >

RE: Re: external storage with dvdi module

Regarding inquiry by Marica Antonacci on Wed, 18 Nov 2015 04:43:47 -0800 Failover scenarios are anticipated in the DVDI module and are being tracked as this issue on github https://github.com/emccode/mesos-module-dvdi/issues/23 The resolution of this issue requires that the underlying volume

RE: Re:

Ah perfect! Thanks for the info! From: Adam Bordelon [a...@mesosphere.io] Sent: 01 June 2015 06:48 To: user@mesos.apache.org Subject: Re: FYI, Mesos will exclude 1GB from what it auto-detects, so that the mesos-slave process and other system processes can use

Re: Re: Please Help me about hadoop on Mesos

On Mon, Jan 27, 2014 at 10:07 AM, HUO Jing huoj...@ihep.ac.cn wrote: So, at the very beginning, if all the resource are assigned to hadoop, and after that, there are always enough jobs in jobtracker, is that meanning that the other framework will never get resource? Is it fair to do so ?