redis-sentinel works by rewriting the sentinel.conf during state changes (failover, new slave added, etc). However, Chef will come along and blow away those state changes during the next convergence.
Redis-sentinel will write configuration and state data back into its configuration file. This creates obvious problems when that config is managed by chef. This cookbook will create the config file once, and then leave a breadcrumb that will guard against the file from being updated again.
This issue is for implementing a similar pattern within this cookbook. Without this, redis-sentinel will not work properly.
redis-sentinel works by rewriting the
sentinel.conf
during state changes (failover, new slave added, etc). However, Chef will come along and blow away those state changes during the next convergence.This is addressed in the open-source redisio cookbook:
This issue is for implementing a similar pattern within this cookbook. Without this, redis-sentinel will not work properly.