• antirez's avatar
    Cluster: set slot error if we receive an update for a busy slot. · 48702e00
    antirez authored
    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.
    48702e00
cluster.c 155 KB