----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/41896/#review112704 -----------------------------------------------------------
docs/high-availability-framework-guide.md (line 81) <https://reviews.apache.org/r/41896/#comment173227> Can you please also identify "odd number" here, such as "three or five instances is typical but should be a odd number" docs/high-availability-framework-guide.md (line 83) <https://reviews.apache.org/r/41896/#comment173196> s/Mesos/Mesos master? docs/high-availability-framework-guide.md (lines 117 - 118) <https://reviews.apache.org/r/41896/#comment173198> What will be the final state of this task? Does the framework need to re-launch this task again even though this task might already been finished in agent. Can you please add some best practise for this case? - Guangya Liu On 一月 5, 2016, 12:09 a.m., Neil Conway wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/41896/ > ----------------------------------------------------------- > > (Updated 一月 5, 2016, 12:09 a.m.) > > > Review request for mesos, Benjamin Hindman, Ben Mahler, and Joris Van > Remoortere. > > > Bugs: MESOS-3936 > https://issues.apache.org/jira/browse/MESOS-3936 > > > Repository: mesos > > > Description > ------- > > Added guide to writing highly available Mesos frameworks. > > > Diffs > ----- > > docs/app-framework-development-guide.md > 4a43a93d080bdac37b8aee91748fea7552a1cc67 > docs/high-availability-framework-guide.md PRE-CREATION > docs/high-availability.md 31aa66220617a3f8606b185ef247c11f00735227 > docs/home.md 6f0f4b9cb9d0da1f9960ebe7f36ce186c1317535 > > Diff: https://reviews.apache.org/r/41896/diff/ > > > Testing > ------- > > Previewed via site-docker. > > Note that there's a lot more that could be said here; also, at some point we > should probably unify the "reconciliation" page with this page, and perhaps > move some of the content in the "high-availability" page here (leaving the > "high-availability" page for the operator-centric parts of configuring Mesos > to run in HA mode). > > > Thanks, > > Neil Conway > >
