Is incompatible slave info signaled by a certain exit code? On Tue, Feb 23, 2016 at 11:15 AM, Vinod Kone <vinodk...@apache.org> wrote:
> > On Tue, Feb 23, 2016 at 8:44 AM, Zhitao Li <zhi...@uber.com> wrote: > >> Can we consider to add a new option like "--auto_recovery_cleanup" which >> would automatically perform the clean up if detected incompatible slave >> info, or change the default behavior for "--recover"? >> > > Wouldn't you want to know that an incompatible slave info was introduced? > What if it was un-intentional? Note that whether slave automatically > deletes the working directory (what you are proposing) or not, the tasks > will be gone. > > One option would be for your startup script (the one that wraps > mesos-slave binary) to contain this logic. > > -- > Zameer Manji > >