antirez a2ff90919f Cluster: set slot error if we receive an update for a busy slot.
By manually modifying nodes configurations in random ways, it is possible
to create the following scenario:

A is serving keys for slot 10
B is manually configured to serve keys for slot 10

A receives an update from B (or another node) where it is informed that
the slot 10 is now claimed by B with a greater configuration epoch,
however A still has keys from slot 10.

With this commit A will put the slot in error setting it in IMPORTING
state, so that redis-trib can detect the issue.
2014-03-11 11:49:47 +01:00
..
2012-04-13 17:52:33 -07:00
2013-01-19 10:59:44 +01:00
2013-01-19 10:59:44 +01:00
2013-01-19 10:59:44 +01:00
2014-03-10 23:01:55 +01:00
2013-05-14 11:23:16 +02:00
2013-01-19 10:59:44 +01:00
2014-02-28 16:00:00 +01:00
2013-12-13 13:10:05 +01:00
2013-01-19 10:59:44 +01:00
2013-01-19 10:59:44 +01:00
2014-01-22 09:54:55 +01:00
2013-07-16 15:43:36 +02:00
2013-12-12 16:33:29 +08:00
2013-08-12 11:38:21 +02:00
2014-03-05 00:41:02 +01:00
2013-01-19 10:59:44 +01:00
2013-07-24 18:59:54 +02:00
2013-07-02 12:08:07 +02:00
2011-07-06 15:22:00 +02:00
2013-05-27 11:44:04 +02:00
2013-09-03 15:15:51 +02:00