summaryrefslogtreecommitdiff
path: root/sentinel.conf
diff options
context:
space:
mode:
authorYubao Liu <Yubao.Liu@gmail.com>2013-11-30 14:14:28 +0800
committerYubao Liu <Yubao.Liu@gmail.com>2013-12-11 15:46:42 +0800
commit6d5fa2e06ce8b35a85715b9960ff5a5e14bc1bdd (patch)
treedd26033c1bf6ec3609ace121a3aeb292c578bd55 /sentinel.conf
parent11120689c4c59b0fdde5446ea40f6abdc215d7c9 (diff)
downloadredis-6d5fa2e06ce8b35a85715b9960ff5a5e14bc1bdd.tar.gz
fix typo in redis.conf and sentinel.conf
Diffstat (limited to 'sentinel.conf')
-rw-r--r--sentinel.conf6
1 files changed, 3 insertions, 3 deletions
diff --git a/sentinel.conf b/sentinel.conf
index 248e76c06..e44342221 100644
--- a/sentinel.conf
+++ b/sentinel.conf
@@ -6,7 +6,7 @@ port 26379
# sentinel monitor <master-name> <ip> <redis-port> <quorum>
#
-# Tells Sentinel to monitor this slave, and to consider it in O_DOWN
+# Tells Sentinel to monitor this master, and to consider it in O_DOWN
# (Objectively Down) state only if at least <quorum> sentinels agree.
#
# Note that whatever is the ODOWN quorum, a Sentinel will require to
@@ -63,7 +63,7 @@ sentinel parallel-syncs mymaster 1
# times the failover timeout.
#
# - The time needed for a slave replicating to a wrong master according
-# to a Sentinel currnet configuration, to be forced to replicate
+# to a Sentinel current configuration, to be forced to replicate
# with the right master, is exactly the failover timeout (counting since
# the moment a Sentinel detected the misconfiguration).
#
@@ -102,7 +102,7 @@ sentinel failover-timeout mymaster 180000
#
# sentinel notification-script <master-name> <script-path>
#
-# Call the specified notification script for any sentienl event that is
+# Call the specified notification script for any sentinel event that is
# generated in the WARNING level (for instance -sdown, -odown, and so forth).
# This script should notify the system administrator via email, SMS, or any
# other messaging system, that there is something wrong with the monitored