curator-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [22/52] [abbrv] git commit: wip
Date Wed, 27 Mar 2013 01:11:17 GMT


Branch: refs/heads/master
Commit: c43ddc5158ce924adf9a569390bef24808fddd92
Parents: e0f9e75
Author: Jordan Zimmerman <>
Authored: Sat Mar 9 22:36:15 2013 -0800
Committer: Jordan Zimmerman <>
Committed: Sat Mar 9 22:36:15 2013 -0800

 .../src/site/confluence/leader-election.confluence |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/curator-recipes/src/site/confluence/leader-election.confluence b/curator-recipes/src/site/confluence/leader-election.confluence
index 85fde0a..ddc1636 100644
--- a/curator-recipes/src/site/confluence/leader-election.confluence
+++ b/curator-recipes/src/site/confluence/leader-election.confluence
@@ -3,7 +3,7 @@ h1. Leader Election
 h2. Description
 In distributed computing, leader election is the process of designating a single process
as the organizer of some task distributed among several computers (nodes). Before the task
is begun, all network nodes are unaware which node will serve as the "leader," or coordinator,
of the task. After a leader election algorithm has been run, however, each node throughout
the network recognizes a particular, unique node as the task leader.
-NOTE: Curator has two leader election recipes. Which one two use depends on your requirements.
+NOTE: Curator has two leader election recipes. Which one to use depends on your requirements.
 h2. Participating Classes
 * LeaderSelector

View raw message