Hello,

I remember when i was running some older mesos version (maybe 0.23.0),
whenever slave restart used to fail either due to adding some new attribute
or announcing different resource than default, I used to cleanup the
/tmp/mesos (mesos working dir) & this used to bring down the existing
executors/tasks.

Yesterday, I noticed that even after cleaning up /tmp/mesos and starting
slaves (registered with different slave id) didn't bring down the existing
executor/tasks. I am running 0.28.0.

I would like to know what has improved in slave recovery process because i
was assuming that i deleted all the information related to checkpointing by
cleaning up /tmp/mesos.

-- 
Regards,
Pradeep Chhetri

Reply via email to