Re: Mesos 0.25.0

On 30 August 2015 at 16:00, Dave Lester wrote: > Hi Niklas, > > Could you create a JIRA issue tracking this release? A great example > would be what was created for the 0.22.0 release and promotes more > transparency IMO about what is going in a release: >

CPU soft lock up on mesos-slave

Hi all, I was running a Mesos cluster on EC2 with c4.8xlarge instance types when one of the status checks failed. We are running Mesos 0.22.1 on ubuntu 14.04, with kernel version 3.13.0-55-generic. EC2 gave us this console output[1]. I did some searching and found similar issues reported here[2]

Re: CPU soft lock up on mesos-slave

Hi Chris, Perhaps you've run into  https://community.nitrous.io/posts/stability-and-a-linux-oom-killer-bug. We ran into similar symptoms that you've described and taking the above as the cause solved all of our issues. Hope this helps! -- Tom Arnfeld Developer // DueDil (+44)

Re: Docker socket path for slave

Hi Tim, I have uploaded new patch, synching with master. Can you please let me know if the patch can make to main trunk? Thanks > On Aug 28, 2015, at 3:53 PM, Timothy Chen wrote: > > Hi Vaibhav, > > Thanks for the ping, sorry as you said there are other work that is >

Re: Is dynamic reservation per role or per framework

Persistent volume is indeed also per role, however that's not explicit. What I mean is that because persistent volume can only be created on reserved resources, it happens to inherit whatever characteristics reservations have. Suppose we were to change dynamic reservation to be per-framework.

Re: How to enable logs when running UT cases

How two way to do this: If use mesos-tests.sh: GLOG_v=1 ./bin/mesos-tests.sh --gtest_filter="xxx" --verbose If use make check: GLOG_v=1 MESOS_VERBOSE=1 make check GTEST_FILTER="xxx" On Tue, Sep 1, 2015 at 1:07 PM, Klaus Ma wrote: > Hi team, > > I’m working on MESOS-3070

Re: How to enable logs when running UT cases

Use ./bin/mesos-test.sh --verbose — Sent from Mailbox On Mon, Aug 31, 2015 at 10:07 PM, Klaus Ma wrote: > Hi team, > I’m working on MESOS-3070 (Master CHECK failure if a framework uses > duplicated task id); the fix was passed in Ubuntu 14.04 but failed at Mac OS, > so is

How to enable logs when running UT cases

Hi team, I’m working on MESOS-3070 (Master CHECK failure if a framework uses duplicated task id); the fix was passed in Ubuntu 14.04 but failed at Mac OS, so is there any parameter to enable logs when run UT cases? So I can check what happened in Mac OS. I export MESOS_VERBOSE, but it seems