Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support for read vs write replicas #69

Closed
snarfed opened this issue Apr 14, 2015 · 5 comments
Closed

support for read vs write replicas #69

snarfed opened this issue Apr 14, 2015 · 5 comments

Comments

@snarfed
Copy link

snarfed commented Apr 14, 2015

first off, thanks for django-redis-cache, we love it!

we have a feature request: we'd love to use a redis replication group with both read only and read/write replicas. any chance you could support that in the future? i'm guessing we'd either provide multiple django cache backends with well-known names, or we'd specify the read vs write endpoints in OPTIONS, and you'd pick the right one for each cache operation. or however you want!

(related to #3 and #31, but not the same.)

thanks in advance!

@sebleier
Copy link
Owner

Hi @snarfed, I have that feature in an unstable 1.0 branch. Once I merge it into master, I'll let you know and close this issue.

@snarfed
Copy link
Author

snarfed commented Apr 14, 2015

woo that's great news! thanks!

@sebleier
Copy link
Owner

This is available on the latest release. More docs coming soon, but the tests should give you a clue on usage. Cheers

@snarfed
Copy link
Author

snarfed commented Jul 16, 2015

yay, thank you @sebleier! can't wait to try it!

@sebleier
Copy link
Owner

If you run into any problems, let me know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants