1. 05 May, 2016 19 commits
  2. 04 May, 2016 7 commits
  3. 02 May, 2016 2 commits
    • antirez's avatar
      Cluster regression test for #3043. · 9c48f28e
      antirez authored
      The test works but is very slow so far, since it involves resharding
      1/5 of all the cluster slots from master 0 to the other 4 masters and
      back into the original master.
      9c48f28e
    • antirez's avatar
      New masters with slots are now targets of migration if others are. · 4fdde78c
      antirez authored
      This fixes issue #3043.
      
      Before this fix, after a complete resharding of a master slots
      to other nodes, the master remains empty and the slaves migrate away
      to other masters with non-zero nodes. However the old master now empty,
      is no longer considered a target for migration, because the system has
      no way to tell it had slaves in the past.
      
      This fix leaves the algorithm used in the past untouched, but adds a
      new rule. When a new or old master which is empty and without slaves,
      are assigend with their first slot, if other masters in the cluster have
      slaves, they are automatically considered to be targets for replicas
      migration.
      4fdde78c
  4. 30 Apr, 2016 1 commit
  5. 25 Apr, 2016 6 commits
  6. 22 Apr, 2016 1 commit
    • therealbill's avatar
      fix for #3187 · 14086a46
      therealbill authored
      I've renamed maxmemoryToString to evictPolicyToString since that is
      more accurate (and easier to mentally connect with the correct data), as
      well as updated the function to user server.maxmemory_policy rather than
      server.maxmemory. Now with a default config it is actually returning
      the correct policy rather than volatile-lru.
      14086a46
  7. 18 Apr, 2016 2 commits
  8. 15 Apr, 2016 2 commits