Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Sentinel doesnt failover chained slaves #1015

mezzatto opened this Issue Mar 19, 2013 · 3 comments


None yet
4 participants

If I have a chained slaves setup, Sentinel doesnt failover them. Like this:

(Master1) -> (Slave1) -> (Slave2)

If Slave1 fails, Slave2 doesnt become slave of Master1, and Master1 has no slaves


antirez commented Mar 25, 2013

Hello, currently Sentinel unfortunately does not support chained slaves at all. It is not currently clear if we'll support this feature. Thanks for reporting, I'll update the documentation (taking this issue open in order to do this task).

Was this issue actually closed in 8d7ffce?

@antirez antirez removed this from the Redis 2.8 milestone May 15, 2017

Hi @antirez,

I have a similar scenario where I would like to have a cascading architecture with failover at the to of the tree.

When I start sentinel, it switches all the slave's connections (regardless to their current master) to the main master and basically undoing all the cascading that I configured.

It would be nice to be able to configure layers for sentinel to keep, and to promote slaves to a higher layer if all the masters in the middle layer are down.

The reason for this architecture is to distribute the load on the master and prevent all the slaves from overflowing it.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment