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 myself. On Sep 23, 2015 7:53 AM, "Paul Bell" <arach...@gmail.com> wrote:
> 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 /tmp/mesos/meta/slaves/latest > > > But I know of no way to make such configuration changes without downtime. > And I'd very much like it if Mesos supported such dynamic changes. I > suppose this would require that the agent consult its default file on > demand, rather than once at start-up. > > Cordially, > > Paul > > On Wed, Sep 23, 2015 at 4:41 AM, Pradeep Chhetri < > pradeep.chhetr...@gmail.com> wrote: > >> Hello all, >> >> I have often faced this problem that whenever i try to add some >> configuration parameter to mesos-slave or change any configuration (eg. add >> a new attribute in mesos-slave), the mesos slave doesnt come up on restart. >> I have to delete the slave.info file and then restart the slave but it >> ends up killing all the docker containers started using mesos. >> >> I was trying to figure out the best way to make such changes without >> making any downtime. >> >> Thank you. >> >> -- >> Pradeep Chhetri >> > >
