rackspace-cookbooks / redis-multi

Chef wrapper cookbook to create redis master/slave server setups
Apache License 2.0
6 stars 6 forks source link

Sentinel config file conflict #7

Open boxidau opened 9 years ago

boxidau commented 9 years ago

Sentinel actually writes runtime information to it's config file which is subsequently overwritten by chef

I propose that we use a "fixed" config file which is managed by chef and a runtime copy of the config which is not chef managed and is used as the source of truth for sentinel.

On any updates to the chef-managed config the sentinel runtime config is also overwritten with the updated chef content and sentinel is reloaded. Otherwise if no changes are made to the chef-managed config the runtime file should just be checked for existence (and copied from the chef managed version if it doesn't exist).

boxidau commented 9 years ago

http://code.flickr.net/2014/07/31/redis-sentinel-at-flickr/

boxidau commented 9 years ago

This probably needs to go upstream

martinb3 commented 9 years ago

Yes, this definitely needs to go upstream @ the redisio cookbook. Upstream still has a few different pieces of sentinel work to do (e.g. support for multiple masters). I'd be much obliged if you would submit an issue there.

brint commented 9 years ago

Redis v3.0.0 has just been released with native clustering support. We will need to re-evaluate how we handle this based on the new version.