This code was added a few months ago by Anton Lindström who I presume is
using it? We don't use swap so it's never been tested in production here.
I'll take a look at it shortly and get a fix out.
Ian
On Tue, Nov 18, 2014 at 6:08 PM, Bjoern Metzdorf bjo...@metzdorf.de wrote:
Hi,
we just ran
Hi,
I'm implementing an executor which is used by the mesos slave to launch
tasks. The tasks are to launch a docker container - this is because I need
more info about the launched container than what the docker containerizer
returns.
Is it OK to block in the executor's launchTask method until the
Hi Janet,
Great to hear you're using Mesos! It's not the best idea to block in callbacks
from the mesos drivers, either in the Executor or Framework, this is because
you won't be notified correctly when other events happen (master failover,
shutdown request, kill task request) as I believe
-- Forwarded message --
From: Ian Downes idow...@twitter.com
Date: Tue, Nov 18, 2014 at 4:27 PM
Subject: Proposed changes to memory usage in ResourceStatistics [MESOS-2104]
To: d...@mesos.apache.org d...@mesos.apache.org
I'd like to propose changes to the protobuf:
1) Correct
Hi Tom,
Thanks for your reply. To be sure I understand correctly, my executor
launches my task. (Which is actually launching a docker container without
using the docker containerizer at all. I'm directly communicating with the
docker daemon in my executor.) When the task has been launched, I send
Hi Janet,
Oh sorry my mistake, I didn't read your email correctly, I thought you were
using the containerizer. What you're doing here is actually going to be quite
difficult to do, the mesos docker containerizer has some quite complex logic
implemented to ensure the slave stays in sync with
6 matches
Mail list logo
