News for hackers. Stuff that matters.
Re:Redis Sentinel design draft 1.1 by simonw on Friday June 29, 2012 @12:34PM (#4177504)
As far as I can tell, the core mechanism here is that the sentinals keep an eye on your redis instances and agree which slave should become a master if your master dies. They then "inform the clients" of the configuration change.

One thing that worries me... normally if I have a configuration setting that might change at runtime I store it in redis! Does anyone have a good way of storing the configuration of where the redis server is in a way that can be updated at runtime (assuming a standard shared-nothing architecture) - without putting it in redis?

Re:Redis Sentinel design draft 1.1 by stock_toaster on Friday June 29, 2012 @04:44PM (#4178998)
Maybe something like doozer[1] or zookeeper[2].

[1]: https://github.com/ha/doozerd

[2]: http://zookeeper.apache.org/

Re:Redis Sentinel design draft 1.1 by mrkurt on Friday June 29, 2012 @03:33PM (#4178611)
In mongo world, you actually store the possible members as app configuration, then the drivers can use them to discover who's currently master. It seems reasonably easy to do the same thing with the Redis sentinels, store addresses for all of them you can and query for the "primary" Redis at startup time.