Hi all, most people are probably familiar with the behaviour of the mesos-agent that refuses to start when it detects incompatible slave information from a previous run in its work directory. There is currently no way of suppressing or pre-emptively avoiding this scenario without manual user intervention.
There has been some prior work towards changing this, i.e. https://issues.apache.org/jira/browse/MESOS-1739 and in particular https://docs.google.com/document/d/1PWv7YIdV3nN2l1oUW7Nybm4KdnxZ7 Px2JGc5UM-PKoQ/edit#heading=h.ygnc486t6w2z but it looks like it is not under active development anymore after parts of it have been implemented. Since I would like to work on this as well, I wrote up another, new proposal to relax this strict behaviour: https://docs.google.com/document/d/1iOENs0JoXPc7sf1NDBCR2tPJ_KxwU4lLtr53SrE5U3Q/edit?usp=sharing As always, any comments and suggestions are welcome and highly valued. Best regards, -- Benno Evers Software Engineer, Mesosphere
