Re: Non-checkpointing frameworks

2016-10-18 Thread Neil Conway
Hi folks, Thanks for the feedback! On Mon, Oct 17, 2016 at 12:44 PM, Zhitao Li wrote: > +1 to both A to B. > > Do we plan to eventually drop non-checkpionted framework support (possibly > in v2) and declare that all frameworks has to operate in this assumption? I think that's worth considering

Re: Non-checkpointing frameworks

2016-10-17 Thread Qian Zhang
Got it, thanks Zameer! Thanks, Qian Zhang On Tue, Oct 18, 2016 at 2:25 AM, Zameer Manji wrote: > Qian, > > Turns out the --checkpoint flag was made default and removed in Mesos 0.22. > > On Sun, Oct 16, 2016 at 4:38 PM, Qian Zhang wrote: > >> and requires operators to enable checkpointing on

Re: Non-checkpointing frameworks

2016-10-17 Thread Zameer Manji
Qian, Turns out the --checkpoint flag was made default and removed in Mesos 0.22. On Sun, Oct 16, 2016 at 4:38 PM, Qian Zhang wrote: > and requires operators to enable checkpointing on the slaves. > > > Just curious why operator needs to enable checkpointing on the slaves (I > do not see an age

Re: Non-checkpointing frameworks

2016-10-17 Thread Zhitao Li
+1 to both A to B. Do we plan to eventually drop non-checkpionted framework support (possibly in v2) and declare that all frameworks has to operate in this assumption? On Mon, Oct 17, 2016 at 1:36 AM, Aaron Carey wrote: > +1 to A and B > > Aaron Carey > Production Engineer - Cloud Pipeline > In

Re: Non-checkpointing frameworks

2016-10-17 Thread Aaron Carey
+1 to A and B Aaron Carey Production Engineer - Cloud Pipeline Industrial Light & Magic London 020 3751 9150 On 17 October 2016 at 00:38, Qian Zhang wrote: > and requires operators to enable checkpointing on the slaves. > > > Just curious why operator needs to enable checkpointing on the slave

Re: Non-checkpointing frameworks

2016-10-16 Thread Qian Zhang
> > and requires operators to enable checkpointing on the slaves. Just curious why operator needs to enable checkpointing on the slaves (I do not see an agent flag for that), I think checkpointing should be enabled in framework level rather than slave. Thanks, Qian Zhang On Sun, Oct 16, 2016 a

Re: Non-checkpointing frameworks

2016-10-15 Thread Zameer Manji
+1 to A and B Aurora has enabled checkpointing for years and requires operators to enable checkpointing on the slaves. On Sat, Oct 15, 2016 at 11:57 AM, Joris Van Remoortere wrote: > I'm in favor of A & B. I find it provides a better "first experience" to > users. > From my experience you usual

Re: Non-checkpointing frameworks

2016-10-15 Thread Joris Van Remoortere
I'm in favor of A & B. I find it provides a better "first experience" to users. >From my experience you usually have to have an explicit reason to not want to checkpoint. Most people assume the semantics provided by the checkpoint behavior is default and it can be a frustrating experience for them