LoL. If not set, it is zero. Ignore my previous response, sorry. @Aditi On Sat, Jun 20, 2015 at 1:11 AM, haosdent <haosd...@gmail.com> wrote:
> default failover_timeout is zero? > > On Sat, Jun 20, 2015 at 1:04 AM, Adam Bordelon <a...@mesosphere.io> wrote: > >> Aha! You also need to set the FrameworkInfo.failover_timeout to a non-zero >> value. If it is 0, then Mesos will instantly shutdown your framework when >> the schedulerdriver disconnects. >> >> On Fri, Jun 19, 2015 at 9:56 AM, haosdent <haosd...@gmail.com> wrote: >> >> > From you gist, I think `reregistered` would be call after driver >> disconnect >> > to master and connect to master again. Not happend when call stop and >> start >> > a new driver with same framework id. You could check out this test case >> > FaultToleranceTest.FrameworkReregister . >> > >> > On Sat, Jun 20, 2015 at 12:31 AM, Vinod Kone <vinodk...@gmail.com> >> wrote: >> > >> > > Can you send us the gist? >> > > >> > > @vinodkone >> > > >> > > > On Jun 19, 2015, at 8:49 AM, Aditi Dixit <aditi96di...@gmail.com> >> > wrote: >> > > > >> > > > Hi, >> > > > Thanks for the responses haosdent and Adam. >> > > > I'm sorry if I wasn't clear enough, but yes, the patch exactly does >> > what >> > > > Adam just mentioned. >> > > > We create 2 instances of the driver and in the second time, set the >> > > > frameworkId in the FrameworkInfo to the id from when we register the >> > > first >> > > > time, and start the driver again. >> > > > This should hopefully satisfy all prerequisites. So my question >> still >> > > > stands. Thanks in advance. >> > > > Regards, >> > > > Aditi Dixit >> > > >> > >> > >> > >> > -- >> > Best Regards, >> > Haosdent Huang >> > >> > > > > -- > Best Regards, > Haosdent Huang > -- Best Regards, Haosdent Huang
