OT-CONTAINER-KIT / redis-operator

A golang based redis operator that will make/oversee Redis standalone/cluster/replication/sentinel mode setup on top of the Kubernetes.
https://ot-redis-operator.netlify.app/
Apache License 2.0
741 stars 207 forks source link

Hi, tested with the latest operator(v0.15.1 v1beta2) and latest redis/redis-sentinel image(v7.0.12). having the same issue. Works without redis password, sdown with redis password. #716

Open elrondwong opened 7 months ago

elrondwong commented 7 months ago
          Hi, tested with the latest operator(v0.15.1 v1beta2) and latest redis/redis-sentinel image(v7.0.12). having the same issue. Works without redis password, sdown with redis password.

Originally posted by @zposloncec7 in https://github.com/OT-CONTAINER-KIT/redis-operator/issues/637#issuecomment-1784732672

elrondwong commented 7 months ago
Running sentinel without TLS mode
ACL_MODE is not true, skipping ACL file modification
Starting  sentinel service .....
7:X 01 Dec 2023 05:55:45.347 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
7:X 01 Dec 2023 05:55:45.347 * Redis version=7.2.1, bits=64, commit=00000000, modified=0, pid=7, just started
7:X 01 Dec 2023 05:55:45.347 * Configuration loaded
7:X 01 Dec 2023 05:55:45.348 * monotonic clock: POSIX clock_gettime
7:X 01 Dec 2023 05:55:45.349 # Failed to write PID file: Permission denied
7:X 01 Dec 2023 05:55:45.349 * Running mode=sentinel, port=26379.
7:X 01 Dec 2023 05:55:45.349 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
7:X 01 Dec 2023 05:55:45.358 * Sentinel new configuration saved on disk
7:X 01 Dec 2023 05:55:45.358 * Sentinel ID is 991b9a8a1bde10055ce7010b59cf2559574bcdaa
7:X 01 Dec 2023 05:55:45.358 # +monitor master myMaster 10.222.1.78 6379 quorum 2
7:X 01 Dec 2023 05:56:15.400 # +sdown master myMaster 10.222.1.78 6379
127.0.0.1:26379> info sentinel
# Sentinel
sentinel_masters:1
sentinel_tilt:0
sentinel_tilt_since_seconds:-1
sentinel_running_scripts:0
sentinel_scripts_queue_length:0
sentinel_simulate_failure_flags:0
master0:name=myMaster,status=sdown,address=10.222.1.78:6379,slaves=0,sentinels=1
bash-5.1$ cat /etc/redis/sentinel.conf
port 26379
daemonize no
pidfile "/var/run/redis-sentinel.pid"
logfile ""
dir "/tmp"

acllog-max-len 128

# sentinel monitor mymaster 127.0.0.1 6379 2
# sentinel down-after-milliseconds mymaster 30000
# sentinel parallel-syncs mymaster 1
# sentinel failover-timeout mymaster 180000
sentinel deny-scripts-reconfig yes
sentinel resolve-hostnames no
sentinel announce-hostnames no
# SENTINEL master-reboot-down-after-period mymaster 0
protected-mode no
sentinel monitor myMaster 10.222.1.78 6379 2

# Generated by CONFIG REWRITE
latency-tracking-info-percentiles 50 99 99.9
user default on nopass sanitize-payload ~* &* +@all
sentinel myid d4d4a7e8b871e03c91c3ac9bf7ede917c89f0cb1
sentinel config-epoch myMaster 0
sentinel leader-epoch myMaster 0
sentinel current-epoch 0