Skip to content

Instantly share code, notes, and snippets.

@wilsolutions

wilsolutions/gist:9749826

Created March 24, 2014 21:43
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save wilsolutions/9749826 to your computer and use it in GitHub Desktop.
Save wilsolutions/9749826 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
gistfile1.txt
I am trying to setup redis sentinel in 2 vms, this is my setup:
- 10.1.8.36 mymaster
- 10.1.8.46 resque (redis.conf = slaveof 10.1.8.36)
- in both mnachines /etc/redis-sentinel.conf
port 26379
sentinel monitor mymaster 10.1.8.36 6379 1
sentinel down-after-milliseconds mymaster 5000
sentinel failover-timeout mymaster 60000
sentinel parallel-syncs mymaster 1
- This is my log:
[3447] 24 Mar 16:26:55.561 # +new-epoch 6
[3447] 24 Mar 16:26:55.561 # +try-failover master mymaster 10.1.8.36 6379
[3447] 24 Mar 16:26:55.561 # +vote-for-leader 0ff5a5f69e7b420a666ca6f10544152e70f4676d 6
[3447] 24 Mar 16:26:55.561 # +elected-leader master mymaster 10.1.8.36 6379
[3447] 24 Mar 16:26:55.561 # +failover-state-select-slave master mymaster 10.1.8.36 6379
[3447] 24 Mar 16:26:55.638 # -failover-abort-no-good-slave master mymaster 10.1.8.36 6379
- However I keep hgetting the following error:
[3447] 24 Mar 16:26:55.638 # -failover-abort-no-good-slave master mymaster 10.1.8.36 6379
- I am not sure why it keeps saying: -failover-abort-no-good-slave master mymaster 10.1.8.36 6379
=P
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment