commit 7094e26af262a736fef577a53dc56bdefc0bb4df
parent 2845ed6c74849095e3a0f84b7738d7350d409713
Author: Ivan Gankevich <igankevich@ya.ru>
Date: Tue, 21 Feb 2017 18:31:12 +0300
Correct a typo in label name.
Diffstat:
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/body.tex b/src/body.tex
@@ -77,10 +77,10 @@ parent nodes, however, failure is detected only for kernels that are sent from
one node to another (local kernels are not considered). High availability is
provided by replicating master kernel to a subordinate node. When any of the
replicas fails, another one is used in place. Detailed explanation of the fail
-over algorithm is provided in Section~\ref{sec:failure-scenoarios}.
+over algorithm is provided in Section~\ref{sec:failure-scenarios}.
\section{Failure scenarios}
-\label{sec:failure-scenoarios}
+\label{sec:failure-scenarios}
Now we discuss failure scenarios and how scheduler can handle it. First, define
clearly relations between sets of daemons and kernels. We named such relations
