You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@storm.apache.org by kn...@apache.org on 2015/11/23 22:08:09 UTC
[30/37] storm git commit: Fixing nits.
Fixing nits.
Project: http://git-wip-us.apache.org/repos/asf/storm/repo
Commit: http://git-wip-us.apache.org/repos/asf/storm/commit/711e36fa
Tree: http://git-wip-us.apache.org/repos/asf/storm/tree/711e36fa
Diff: http://git-wip-us.apache.org/repos/asf/storm/diff/711e36fa
Branch: refs/heads/master
Commit: 711e36fafcac33f4fb7238001ea8bc678fab2d56
Parents: 387232c
Author: Kyle Nusbaum <Ky...@gmail.com>
Authored: Thu Nov 19 11:08:52 2015 -0600
Committer: Kyle Nusbaum <Ky...@gmail.com>
Committed: Thu Nov 19 11:08:52 2015 -0600
----------------------------------------------------------------------
docs/documentation/Pacemaker.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/storm/blob/711e36fa/docs/documentation/Pacemaker.md
----------------------------------------------------------------------
diff --git a/docs/documentation/Pacemaker.md b/docs/documentation/Pacemaker.md
index f82f23d..24e3e7f 100644
--- a/docs/documentation/Pacemaker.md
+++ b/docs/documentation/Pacemaker.md
@@ -91,9 +91,9 @@ PacemakerServer {
### Fault Tolerance
-Pacemaker runs as a single daemon instance currently. This makes it a potential Single Point of Failure.
+Pacemaker runs as a single daemon instance, making it a potential Single Point of Failure.
-If Pacemaker becomes unreachable by Nimbus, through crash or partition, the workers will continue to run and Nimbus will repeatedly attempt to reconnect. Nimbus functionality will be disrupted, but the topologies themselves will continue to run.
+If Pacemaker becomes unreachable by Nimbus, through crash or network partition, the workers will continue to run, and Nimbus will repeatedly attempt to reconnect. Nimbus functionality will be disrupted, but the topologies themselves will continue to run.
In case of partition of the cluster where Nimbus and Pacemaker are on the same side of the partition, the workers that are on the other side of the partition will not be able to heartbeat, and Nimbus will reschedule the tasks elsewhere. This is probably what we want to happen anyway.