From b01802415d5e3682688acf84ad87013cf3d4ba3b Mon Sep 17 00:00:00 2001 From: Drew DeVault Date: Thu, 21 Mar 2024 10:43:01 +0100 Subject: [PATCH] sentinel.conf: redis => redict --- sentinel.conf | 60 +++++++++++++++++++++++++-------------------------- 1 file changed, 30 insertions(+), 30 deletions(-) diff --git a/sentinel.conf b/sentinel.conf index b7b3604f0..caf1f85c3 100644 --- a/sentinel.conf +++ b/sentinel.conf @@ -9,15 +9,15 @@ protected-mode no # The port that this sentinel instance will run on port 26379 -# By default Redis Sentinel does not run as a daemon. Use 'yes' if you need it. -# Note that Redis will write a pid file in /var/run/redis-sentinel.pid when +# By default redict Sentinel does not run as a daemon. Use 'yes' if you need it. +# Note that redict will write a pid file in /var/run/redict-sentinel.pid when # daemonized. daemonize no -# When running daemonized, Redis Sentinel writes a pid file in -# /var/run/redis-sentinel.pid by default. You can specify a custom pid file +# When running daemonized, redict Sentinel writes a pid file in +# /var/run/redict-sentinel.pid by default. You can specify a custom pid file # location here. -pidfile /var/run/redis-sentinel.pid +pidfile /var/run/redict-sentinel.pid # Specify the server verbosity level. # This can be one of: @@ -67,12 +67,12 @@ logfile "" # dir # Every long running process should have a well-defined working directory. -# For Redis Sentinel to chdir to /tmp at startup is the simplest thing +# For redict Sentinel to chdir to /tmp at startup is the simplest thing # for the process to don't interfere with administrative tasks such as # unmounting filesystems. dir /tmp -# sentinel monitor +# sentinel monitor # # Tells Sentinel to monitor this master, and to consider it in O_DOWN # (Objectively Down) state only if at least sentinels agree. @@ -94,16 +94,16 @@ sentinel monitor mymaster 127.0.0.1 6379 2 # sentinel auth-pass # # Set the password to use to authenticate with the master and replicas. -# Useful if there is a password set in the Redis instances to monitor. +# Useful if there is a password set in the redict instances to monitor. # # Note that the master password is also used for replicas, so it is not # possible to set a different password in masters and replicas instances # if you want to be able to monitor these instances with Sentinel. # -# However you can have Redis instances without the authentication enabled -# mixed with Redis instances requiring the authentication (as long as the +# However you can have redict instances without the authentication enabled +# mixed with redict instances requiring the authentication (as long as the # password set is the same for all the instances requiring the password) as -# the AUTH command will have no effect in Redis instances with authentication +# the AUTH command will have no effect in redict instances with authentication # switched off. # # Example: @@ -113,10 +113,10 @@ sentinel monitor mymaster 127.0.0.1 6379 2 # sentinel auth-user # # This is useful in order to authenticate to instances having ACL capabilities, -# that is, running Redis 6.0 or greater. When just auth-pass is provided the -# Sentinel instance will authenticate to Redis using the old "AUTH " +# that is, running redict 6.0 or greater. When just auth-pass is provided the +# Sentinel instance will authenticate to redict using the old "AUTH " # method. When also an username is provided, it will use "AUTH ". -# In the Redis servers side, the ACL to provide just minimal access to +# In the redict servers side, the ACL to provide just minimal access to # Sentinel instances, should be configured along the following lines: # # user sentinel-user >somepassword +client +subscribe +publish \ @@ -132,8 +132,8 @@ sentinel monitor mymaster 127.0.0.1 6379 2 # Default is 30 seconds. sentinel down-after-milliseconds mymaster 30000 -# IMPORTANT NOTE: starting with Redis 6.2 ACL capability is supported for -# Sentinel mode, please refer to the Redis website https://redis.io/topics/acl +# IMPORTANT NOTE: starting with redict 6.2 ACL capability is supported for +# Sentinel mode, please refer to the redict website https://redict.io/topics/acl # for more details. # Sentinel's ACL users are defined in the following format: @@ -144,9 +144,9 @@ sentinel down-after-milliseconds mymaster 30000 # # user worker +@admin +@connection ~* on >ffa9203c493aa99 # -# For more information about ACL configuration please refer to the Redis -# website at https://redis.io/topics/acl and redis server configuration -# template redis.conf. +# For more information about ACL configuration please refer to the redict +# website at https://redict.io/topics/acl and redict server configuration +# template redict.conf. # ACL LOG # @@ -164,9 +164,9 @@ acllog-max-len 128 # ACL file, the server will refuse to start. # # The format of the external ACL user file is exactly the same as the -# format that is used inside redis.conf to describe users. +# format that is used inside redict.conf to describe users. # -# aclfile /etc/redis/sentinel-users.acl +# aclfile /etc/redict/sentinel-users.acl # requirepass # @@ -174,9 +174,9 @@ acllog-max-len 128 # so Sentinel will try to authenticate with the same password to all the # other Sentinels. So you need to configure all your Sentinels in a given # group with the same "requirepass" password. Check the following documentation -# for more info: https://redis.io/topics/sentinel +# for more info: https://redict.io/topics/sentinel # -# IMPORTANT NOTE: starting with Redis 6.2 "requirepass" is a compatibility +# IMPORTANT NOTE: starting with redict 6.2 "requirepass" is a compatibility # layer on top of the ACL system. The option effect will be just setting # the password for the default user. Clients will still authenticate using # AUTH as usually, or more explicitly with AUTH default @@ -259,7 +259,7 @@ sentinel failover-timeout mymaster 180000 # 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 -# Redis systems. +# redict systems. # # The script is called with just two arguments: the first is the event type # and the second the event description. @@ -269,7 +269,7 @@ sentinel failover-timeout mymaster 180000 # # Example: # -# sentinel notification-script mymaster /var/redis/notify.sh +# sentinel notification-script mymaster /var/redict/notify.sh # CLIENTS RECONFIGURATION SCRIPT # @@ -294,7 +294,7 @@ sentinel failover-timeout mymaster 180000 # # Example: # -# sentinel client-reconfig-script mymaster /var/redis/reconfig.sh +# sentinel client-reconfig-script mymaster /var/redict/reconfig.sh # SECURITY # @@ -305,13 +305,13 @@ sentinel failover-timeout mymaster 180000 sentinel deny-scripts-reconfig yes -# REDIS COMMANDS RENAMING (DEPRECATED) +# redict COMMANDS RENAMING (DEPRECATED) # # WARNING: avoid using this option if possible, instead use ACLs. # -# Sometimes the Redis server has certain commands, that are needed for Sentinel +# Sometimes the redict server has certain commands, that are needed for Sentinel # to work correctly, renamed to unguessable strings. This is often the case -# of CONFIG and SLAVEOF in the context of providers that provide Redis as +# of CONFIG and SLAVEOF in the context of providers that provide redict as # a service, and don't want the customers to reconfigure the instances outside # of the administration console. # @@ -335,7 +335,7 @@ sentinel deny-scripts-reconfig yes # HOSTNAMES SUPPORT # # Normally Sentinel uses only IP addresses and requires SENTINEL MONITOR -# to specify an IP address. Also, it requires the Redis replica-announce-ip +# to specify an IP address. Also, it requires the redict replica-announce-ip # keyword to specify only IP addresses. # # You may enable hostnames support by enabling resolve-hostnames. Note