gvsafronov/futriix
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

several redis->keydb changes in sentinel.conf

Browse Source 
Former-commit-id: d2ef0594711c83ec9223d2e3b26fce9b5a4f685f
This commit is contained in:
christianEQ 2021-06-11 19:16:33 +00:00
parent 974dc4918a
commit 2c78e8c046
1 changed files with 24 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
sentinel.conf
View File

@ -20,12 +20,12 @@
# The port that this sentinel instance will run on # The port that this sentinel instance will run on
port 26379 port 26379
# By default Redis Sentinel does not run as a daemon. Use 'yes' if you need it. # By default KeyDB Sentinel does not run as a daemon. Use 'yes' if you need it.
# Note that Redis will write a pid file in /var/run/keydb-sentinel.pid when # Note that KeyDB will write a pid file in /var/run/keydb-sentinel.pid when
# daemonized. # daemonized.
daemonize no daemonize no
# When running daemonized, Redis Sentinel writes a pid file in # When running daemonized, KeyDB Sentinel writes a pid file in
# /var/run/keydb-sentinel.pid by default. You can specify a custom pid file # /var/run/keydb-sentinel.pid by default. You can specify a custom pid file
# location here. # location here.
pidfile /var/run/keydb-sentinel.pid pidfile /var/run/keydb-sentinel.pid
@ -59,7 +59,7 @@ logfile ""
# dir <working-directory> # dir <working-directory>
# Every long running process should have a well-defined working directory. # 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 KeyDB Sentinel to chdir to /tmp at startup is the simplest thing
# for the process to don't interfere with administrative tasks such as # for the process to don't interfere with administrative tasks such as
# unmounting filesystems. # unmounting filesystems.
dir /tmp dir /tmp
@ -86,16 +86,16 @@ sentinel monitor mymaster 127.0.0.1 6379 2
# sentinel auth-pass <master-name> <password> # sentinel auth-pass <master-name> <password>
# #
# Set the password to use to authenticate with the master and replicas. # 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 KeyDB instances to monitor.
# #
# Note that the master password is also used for replicas, so it is not # 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 # possible to set a different password in masters and replicas instances
# if you want to be able to monitor these instances with Sentinel. # if you want to be able to monitor these instances with Sentinel.
# #
# However you can have Redis instances without the authentication enabled # However you can have KeyDB instances without the authentication enabled
# mixed with Redis instances requiring the authentication (as long as the # mixed with KeyDB instances requiring the authentication (as long as the
# password set is the same for all the instances requiring the password) as # 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 KeyDB instances with authentication
# switched off. # switched off.
# #
# Example: # Example:
@ -105,10 +105,10 @@ sentinel monitor mymaster 127.0.0.1 6379 2
# sentinel auth-user <master-name> <username> # sentinel auth-user <master-name> <username>
# #
# This is useful in order to authenticate to instances having ACL capabilities, # 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 # that is, running KeyDB 6.0 or greater. When just auth-pass is provided the
# Sentinel instance will authenticate to Redis using the old "AUTH <pass>" # Sentinel instance will authenticate to KeyDB using the old "AUTH <pass>"
# method. When also an username is provided, it will use "AUTH <user> <pass>". # method. When also an username is provided, it will use "AUTH <user> <pass>".
# In the Redis servers side, the ACL to provide just minimal access to # In the KeyDB servers side, the ACL to provide just minimal access to
# Sentinel instances, should be configured along the following lines: # Sentinel instances, should be configured along the following lines:
# #
# user sentinel-user >somepassword +client +subscribe +publish \ # user sentinel-user >somepassword +client +subscribe +publish \
@ -125,7 +125,7 @@ sentinel monitor mymaster 127.0.0.1 6379 2
sentinel down-after-milliseconds mymaster 30000 sentinel down-after-milliseconds mymaster 30000
# IMPORTANT NOTE: starting with KeyDB 6.2 ACL capability is supported for # IMPORTANT NOTE: starting with KeyDB 6.2 ACL capability is supported for
# Sentinel mode, please refer to the KeyDB website https://redis.io/topics/acl # Sentinel mode, please refer to the Redis website https://redis.io/topics/acl
# for more details. # for more details.
# Sentinel's ACL users are defined in the following format: # Sentinel's ACL users are defined in the following format:
@ -137,8 +137,8 @@ sentinel down-after-milliseconds mymaster 30000
# user worker +@admin +@connection ~* on >ffa9203c493aa99 # user worker +@admin +@connection ~* on >ffa9203c493aa99
# #
# For more information about ACL configuration please refer to the Redis # For more information about ACL configuration please refer to the Redis
# website at https://redis.io/topics/acl and redis server configuration # website at https://redis.io/topics/acl and KeyDB server configuration
# template redis.conf. # template keydb.conf.
# ACL LOG # ACL LOG
# #
@ -156,9 +156,9 @@ acllog-max-len 128
# ACL file, the server will refuse to start. # ACL file, the server will refuse to start.
# #
# The format of the external ACL user file is exactly the same as the # 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 keydb.conf to describe users.
# #
# aclfile /etc/redis/sentinel-users.acl # aclfile /etc/keydb/sentinel-users.acl
# requirepass <password> # requirepass <password>
# #
@ -168,7 +168,7 @@ acllog-max-len 128
# group with the same "requirepass" password. Check the following documentation # group with the same "requirepass" password. Check the following documentation
# for more info: https://redis.io/topics/sentinel # for more info: https://redis.io/topics/sentinel
# #
# IMPORTANT NOTE: starting with Redis 6.2 "requirepass" is a compatibility # IMPORTANT NOTE: starting with KeyDB 6.2 "requirepass" is a compatibility
# layer on top of the ACL system. The option effect will be just setting # 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 # the password for the default user. Clients will still authenticate using
# AUTH <password> as usually, or more explicitly with AUTH default <password> # AUTH <password> as usually, or more explicitly with AUTH default <password>
@ -251,7 +251,7 @@ sentinel failover-timeout mymaster 180000
# generated in the WARNING level (for instance -sdown, -odown, and so forth). # generated in the WARNING level (for instance -sdown, -odown, and so forth).
# This script should notify the system administrator via email, SMS, or any # This script should notify the system administrator via email, SMS, or any
# other messaging system, that there is something wrong with the monitored # other messaging system, that there is something wrong with the monitored
# Redis systems. # KeyDB systems.
# #
# The script is called with just two arguments: the first is the event type # The script is called with just two arguments: the first is the event type
# and the second the event description. # and the second the event description.
@ -261,7 +261,7 @@ sentinel failover-timeout mymaster 180000
# #
# Example: # Example:
# #
# sentinel notification-script mymaster /var/redis/notify.sh # sentinel notification-script mymaster /var/keydb/notify.sh
# CLIENTS RECONFIGURATION SCRIPT # CLIENTS RECONFIGURATION SCRIPT
# #
@ -286,7 +286,7 @@ sentinel failover-timeout mymaster 180000
# #
# Example: # Example:
# #
# sentinel client-reconfig-script mymaster /var/redis/reconfig.sh # sentinel client-reconfig-script mymaster /var/keydb/reconfig.sh
# SECURITY # SECURITY
# #
@ -297,11 +297,11 @@ sentinel failover-timeout mymaster 180000
sentinel deny-scripts-reconfig yes sentinel deny-scripts-reconfig yes
# REDIS COMMANDS RENAMING # KEYDB COMMANDS RENAMING
# #
# Sometimes the Redis server has certain commands, that are needed for Sentinel # Sometimes the KeyDB server has certain commands, that are needed for Sentinel
# to work correctly, renamed to unguessable strings. This is often the case # 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 KeyDB as
# a service, and don't want the customers to reconfigure the instances outside # a service, and don't want the customers to reconfigure the instances outside
# of the administration console. # of the administration console.
# #
@ -325,7 +325,7 @@ sentinel deny-scripts-reconfig yes
# HOSTNAMES SUPPORT # HOSTNAMES SUPPORT
# #
# Normally Sentinel uses only IP addresses and requires SENTINEL MONITOR # 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 KeyDB replica-announce-ip
# keyword to specify only IP addresses. # keyword to specify only IP addresses.
# #
# You may enable hostnames support by enabling resolve-hostnames. Note # You may enable hostnames support by enabling resolve-hostnames. Note