----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/18155/#review34745 -----------------------------------------------------------
Thanks for this Tom. I will get this committed, once the raised issues are addressed. docs/high-availability.md <https://reviews.apache.org/r/18155/#comment64991> kill white space. docs/high-availability.md <https://reviews.apache.org/r/18155/#comment64992> kill white space. docs/high-availability.md <https://reviews.apache.org/r/18155/#comment64996> s/leader,/leader/ docs/high-availability.md <https://reviews.apache.org/r/18155/#comment64997> s/leader,/leader./ ? docs/high-availability.md <https://reviews.apache.org/r/18155/#comment65000> Kill WS. Also this sentence doesn't read correctly to me. Can we rephrase this? How about? Masters enter leaderless state irrespective of whether they are a leader or not before the disconnection. docs/high-availability.md <https://reviews.apache.org/r/18155/#comment65002> s/, connected to ZooKeeeper,// docs/high-availability.md <https://reviews.apache.org/r/18155/#comment65005> This is giving away too much of the internals. How about? Otherwise, the disconnected backup waits to reconnect with ZooKeeper and possibly get elected as the new leading master. - Vinod Kone On Feb. 14, 2014, 11:50 p.m., Tom Galloway wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/18155/ > ----------------------------------------------------------- > > (Updated Feb. 14, 2014, 11:50 p.m.) > > > Review request for mesos, Dave Lester and Vinod Kone. > > > Repository: mesos-git > > > Description > ------- > > Updated version of high availability doc. > > > Diffs > ----- > > docs/high-availability.md 77af5d5 > > Diff: https://reviews.apache.org/r/18155/diff/ > > > Testing > ------- > > > Thanks, > > Tom Galloway > >
