therealbill b04184f34c Making sentinel flush config on +slave
Originally, only the +slave event which occurs when a slave is
reconfigured during sentinelResetMasterAndChangeAddress triggers a flush
of the config to disk.  However, newly discovered slaves don't
apparently trigger this flush but do trigger the +slave event issuance.

So if you start up a sentinel, add a master, then add a slave to the
master (as a way to reproduce it) you'll see the +slave event issued,
but the sentinel config won't be updated with the known-slave entry.

This change makes sentinel do the flush of the config if a new slave is
deteted in sentinelRefreshInstanceInfo.
2015-05-04 12:54:13 +02:00
..
2012-04-13 17:52:33 -07:00
2014-09-29 06:49:07 -04:00
2014-08-08 10:43:54 +02:00
2015-01-19 14:10:12 -05:00
2015-03-30 12:17:46 +02:00
2014-12-14 12:25:42 +02:00
2015-03-04 11:48:19 -08:00
2014-07-02 17:04:14 +02:00
2014-08-08 14:54:02 +02:00
2015-02-17 11:33:08 -05:00
2014-08-08 10:05:32 +02:00
2015-01-19 14:10:12 -05:00
2015-04-27 12:07:49 +02:00
2015-04-27 12:07:49 +02:00
2015-02-03 15:42:56 +01:00
2014-07-02 16:31:22 +02:00
2011-07-06 15:22:00 +02:00
2015-01-02 11:16:08 -05:00
2015-04-29 10:33:21 +02:00