From 9ab104933eb2d6bf56c3c29ad43608eda9d4c716 Mon Sep 17 00:00:00 2001 From: Scott Lystig Fritchie Date: Mon, 20 Apr 2015 20:32:20 +0900 Subject: [PATCH] WIP: more restructuring --- doc/src.high-level/high-level-chain-mgr.tex | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/src.high-level/high-level-chain-mgr.tex b/doc/src.high-level/high-level-chain-mgr.tex index 11dd5d5..3426caf 100644 --- a/doc/src.high-level/high-level-chain-mgr.tex +++ b/doc/src.high-level/high-level-chain-mgr.tex @@ -658,7 +658,7 @@ all members would be invalid and therefore would not move itself out of wedged state. In very general terms, this requirement for a quorum majority of surviving participants is also a requirement for Paxos, Raft, and ZAB. See Section~\ref{sec:split-brain-management} for a -proposal to handle ``split brain'' scenarios while in CPU mode. +proposal to handle ``split brain'' scenarios while in CP mode. \end{itemize} @@ -670,11 +670,13 @@ with epochs numbered by $E+\delta$ (where $\delta > 0$). The distribution of the $E+\delta$ projections will bring all visible participants into the new epoch $E+delta$ and then into consensus. -The remainder of this section follows the same pattern as +The next portion of this section follows the same pattern as Section~\ref{sec:phases-of-projection-change}: network monitoring, calculating new projections, writing projections, then perhaps adopting the newest projection (which may or may not be the projection that we just wrote). +Beginning with Section~9.5\footnote{TODO correction needed?}, we will +explore TODO topics. \subsubsection{Aside: origin of the analogy to humming a song}