From e0d4146620b841ad11e981e4cdb335cb34951895 Mon Sep 17 00:00:00 2001 From: antirez Date: Thu, 11 Aug 2016 19:53:01 +0200 Subject: [PATCH] Sentinel example config: warn about protected mode. --- sentinel.conf | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/sentinel.conf b/sentinel.conf index 39d1044e2..0e1b266ed 100644 --- a/sentinel.conf +++ b/sentinel.conf @@ -1,5 +1,21 @@ # Example sentinel.conf +# *** IMPORTANT *** +# +# By default Sentinel will not be reachable from interfaces different than +# localhost, either use the 'bind' directive to bind to a list of network +# interfaces, or disable protected mode with "protected-mode no" by +# adding it to this configuration file. +# +# Before doing that MAKE SURE the instance is protected from the outside +# world via firewalling or other means. +# +# For example you may use one of the following: +# +# bind 127.0.0.1 192.168.1.1 +# +# protected-mode no + # port # The port that this sentinel instance will run on port 26379 @@ -178,4 +194,3 @@ sentinel failover-timeout mymaster 180000 # # sentinel client-reconfig-script mymaster /var/redis/reconfig.sh -