Correct, you cannot currently do this. Can you share the what motivates this need? Do you plan on iterating rapidly on the executor in production?
In general, one of the principles of a system like Aurora is to embrace the reality that components can be restarted without warning; which enables non-disruptive infrastructure upgrades. On Thu, Apr 7, 2016 at 7:38 PM, Zhitao Li <zhitaoli...@gmail.com> wrote: > Hi, > > I'm writing to see whether anyone can share some real life experience about > managing the thermos executor, especially about upgrading it fleet-wise. > > > AFAICT, we cannot upgrade thermos executor w/o restarting the running task > because Mesos does now allow executor to be restarted/replaced without > losing tasks belonging to it. > > We are thinking about building such capability in Mesos and possibly extend > it to Aurora. Given this seems like an involved project, I'd like to gather > some feedback from the community on whether people consider this valuable. > > Thanks. > > -- > Cheers, > > Zhitao Li >
