Re: Running mesos-execute inside docker.

Hi Giulio, Can you share your exact docker commands to start the mesos slave and master? Thanks! Tim On Thu, May 21, 2015 at 12:17 PM, Giulio Eulisse giulio.euli...@cern.ch wrote: Mmm, no this does not seem to work. The message is still there. Any other suggestions? -- Ciao, Giulio On

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

Failed to make check and run example framework

@ 0x85ba69 (unknown) I0601 22:45:29.976155 14327 exec.cpp:450] Slave exited, but framework has checkpointing enabled. Waiting 15mins to reconnect with slave 20150601-224223-2574952640-39385-12655-S0 make[3]: *** [check-local] Aborted (core dumped) make[3]: Leaving directory `/root/mesos-0.22.1

EXECUTOR_SIGNAL_ESCALATION_TIMEOUT vs EXECUTOR_SHUTDOWN_GRACE_PERIOD vs docker_stop_timeout

Hi, EXECUTOR_SIGNAL_ESCALATION_TIMEOUT is set to 3 seconds, hard-coded. EXECUTOR_SHUTDOWN_GRACE_PERIOD has a default of 5, and can be configured docker_stop_timeout - default of 0, configurable as well I am running a jobsystem app that needs to clean up and write back some data before it

Re: Failed to make check and run example framework

@ 0x7ffe4bb21d1d __libc_start_main @ 0x85ba69 (unknown) I0601 22:45:29.976155 14327 exec.cpp:450] Slave exited, but framework has checkpointing enabled. Waiting 15mins to reconnect with slave 20150601-224223-2574952640-39385-12655-S0 make[3]: *** [check-local] Aborted (core

Re: Failed to make check and run example framework

checkpointing enabled. Waiting 15mins to reconnect with slave 20150601-224223-2574952640-39385-12655-S0 make[3]: *** [check-local] Aborted (core dumped) make[3]: Leaving directory `/root/mesos-0.22.1/build/src' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/root/mesos-0.22.1/build/src

[DISCUSS] Renaming Mesos Slave

There has been much discussion about finding a less offensive name than Slave, and many of these thoughts have been captured in https://issues.apache.org/jira/browse/MESOS-1478 I would like to open up the discussion on this topic for one week, and if we cannot arrive at a lazy consensus, I will

Re: [DISCUSS] Renaming Mesos Slave

+1 1. Mesos Worker [node/host/machine] 2. Mesos Worker [process] 3. No, master/worker seems to address the issue with less changes. 4. Begin using the new name ASAP, add a disambiguation to the docs, and change old references over time. Fixing the official name, even before changes are in

Re: Failed to make check and run example framework

Thanks Haosdent and Ian. But in my machine, I already have perf installed, so I am not sure why those test cases still failed. # rpm -qa | grep perf perf-2.6.32-431.el6.x86_64 # which perf /usr/bin/perf And can you please let me know why my example C++ framework works as normal?

Re: Failed to make check and run example framework

Perf is specific to the kernel version and different versions have different flags and output formats. Specifically, the code requires a kernel release = 2.6.39 but you're running a 2.6.32 kernel: your version of perf is not currently supported and you should skip those tests. The only effect of

Re: Failed to make check and run example framework

I reran the check with GTEST_FILTER=-Perf* make check, but it failed again in another place: [ RUN ] UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup -bash: /sys/fs/cgroup/cpu/mesos/container/cgroup.procs: No such file or directory mkdir: cannot create directory

Re: EXECUTOR_SIGNAL_ESCALATION_TIMEOUT vs EXECUTOR_SHUTDOWN_GRACE_PERIOD vs docker_stop_timeout

+1, I'd like to know that also. 2015-06-01 23:36 GMT+08:00 Maciej Strzelecki maciej.strzele...@crealytics.com: Hi, EXECUTOR_SIGNAL_ESCALATION_TIMEOUT is set to 3 seconds, hard-coded. EXECUTOR_SHUTDOWN_GRACE_PERIOD has a default of 5, and can be configured docker_stop_timeout -