![]() 01 Jul 01:38:43.368 * Background saving terminated with success 01 Jul 01:38:43.277 * RDB: 0 MB of memory used by copy-on-write 01 Jul 01:38:43.275 * Background saving started by pid 21 01 Jul 01:38:43.275 * Starting BGSAVE for SYNC with target: disk 01 Jul 01:34:45.808 * Background saving terminated with success 01 Jul 01:34:45.799 * RDB: 0 MB of memory used by copy-on-write 01 Jul 01:34:45.797 * Background saving started by pid 20 01 Jul 01:34:45.796 * Starting BGSAVE for SYNC with target: disk 01 Jul 01:13:58.252 * The server is now ready to accept connections on port 6380 01 Jul 01:13:58.252 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128. Redis must be restarted after THP is disabled. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. This will create latency and memory usage issues with Redis. 01 Jul 01:13:58.252 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. To fix this issue add 'vm.overcommit_memory = 1' to /etc/nf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. 01 Jul 01:13:58.252 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 01 Jul 01:38:42.288 # Executing user requested FAILOVER of 'redis-holt-overflow' Not sure how to proceed determining what the problem is. I'm fairly experienced with Sentinel, but rather new to Docker. Looking at THIS post and there does not seem to be any reason why Sentinel would consider the Redis instances invalid. I looked at logs for the master and slave and see nothing abnormal. ![]() I can also monitor both Redis instances and see SENTINEL pings and info requests. from inside the Docker container) and can remotely execute the slaveof command. ![]() I can run redis-cli from the Sentinel host (i.e. I'm running all 3 of the procs in Docker containers, but I'm not sure how that could cause the problem. This doesn't make sense because there doesn't seem to be any trouble with network communication from the Sentinel host to either of the Redis hosts. ![]() It seems like the Slave is not getting the promotion command. But when I issue the SENTINEL FAILVER command Sentinel gets stuck in the state +failover-state-wait-promotion for a few minutes. Everything seems to be working properly including failover when the master is killed. I have one Redis master, one slave, and one Sentinel monitoring them. Redis Sentinel manual failover command timesout ![]()
0 Comments
Leave a Reply. |