Are you using systemd? There is a known issue with slave recovery on
systemd. I'm on mobile or I would link you to the last thread around this
but there is a line you can add to the config that is supposed to fix it.
Whether it will fix it is another matter. I am fighting this issue at work
Hi Pradeep,
Perhaps I am speaking to a slightly different point, but when I change
/etc/default/mesos-slave to add a new attribute, I have to remove file
/tmp/mesos/meta/slaves/latest.
IIRC, mesos-slave itself, in failing to start after such a change, tells me
to do this:
rm -f
I believe Brian might be referring to the "KillMode" in the systemd unit
file:
# the default is cgroup, which means kill all processes
# in the control group of this process, which is not
# what you'd want
KillMode=process
On Wed, Sep 23, 2015 at 8:11 AM, Brian Devins wrote:
Thank you for the replies.
Paul, I am talking the about the same directory. There is a file named
slave.info inside /tmp/mesos/meta/slaves/latest and this needs to be
cleaned before starting mesos slave with a configuration change.
No i am not using systemd. It is basically sysvinit which is
We are adding better support for systemd in 0.25. The ticket is MESOS-3425.
Naturally this is still somewhat experimental, but we would love your
feedback.
We will add some documentation on recommended setups on systemd.
With the changes going into 0.25 you should be able to launch your slave
5 matches
Mail list logo