antirez 794fc4c9a8 Sentinel: persist its unique ID across restarts.
Previously Sentinels always changed unique ID across restarts, relying
on the server.runid field. This is not a good idea, and forced Sentinel
to rely on detection of duplicated Sentinels and a potentially dangerous
clean-up and re-add operation of the Sentinel instance that was
rebooted.

Now the ID is generated at the first start and persisted in the
configuration file, so that a given Sentinel will have its unique
ID forever (unless the configuration is manually deleted or there is a
filesystem corruption).
2015-05-06 16:19:14 +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-20 23:03:34 +08: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