Great thread, guys. Cheers, Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Brenden Matthews <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Wednesday, May 29, 2013 9:39 AM To: "[email protected]" <[email protected]> Subject: Re: [DISCUSS] Slave restart -- 0.13.x branch >Sounds good! I'd probably target 0.14.x for my Hadoop changes rather than >0.13.x. > > >On Tue, May 28, 2013 at 2:00 PM, Vinod Kone <[email protected]> wrote: > >> Hi folks, >> >> We are planning to release a new feature (called "Slave Restart") that >> allows organizations to upgrade mesos without disrupting the running >>tasks. >> Previously, when the slave process was stopped for an upgrade, the tasks >> running on that slave committed suicide. With the new feature, the tasks >> can keep running and connect back to the upgraded slave, when it >>restarts. >> >> Since this feature includes a huge amount of code change, we would like >>to >> create a new branch (0.13.x). The new branch helps us to commit bug >>fixes >> easily, test the feature and also unblocks people from committing other >> major changes/features to master/trunk. We have been testing "Slave >> Restart" feature for a while, but need some more time to iron out some >> kinks. Note that, any bug fixes that relate to "Slave Restart" will go >>to >> both "master" and "0.13.x". >> >> Let us know if you have any questions/concerns. >>
