Redis driver does not failover to slave when master fails
Bug #1367020 reported by
Kurt Griffiths
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zaqar |
Fix Released
|
High
|
prashanth raghu |
Bug Description
Looks like we just need to do a tiny bit of coding to add support for Sentinel, and this will work great.
* Add the ability to configure Sentinel support in zaqar.conf
* Read that config and use it to construct a Sentinel instance and discover the master in lieu of instantiating StrictRedis directly.
* Test master-slave failover with the above and see if the retry decorator needs to do anything to find the new slave, or if redis-py does it automagically.
Changed in zaqar: | |
status: | New → Triaged |
importance: | Undecided → Critical |
assignee: | nobody → Fei Long Wang (flwang) |
milestone: | none → juno-rc1 |
description: | updated |
no longer affects: | zaqar/juno |
Changed in zaqar: | |
milestone: | next → juno-rc2 |
Changed in zaqar: | |
milestone: | juno-rc2 → 2014.2 |
To post a comment you must log in.
I don't think this bug is a release blocker, that said, it's quite important to get it done asap.
I've set the priority to high. As soon as the patch lands, we can backport it to the stable branch.