1. 05 May, 2016 11 commits
  2. 11 Mar, 2016 1 commit
  3. 10 Feb, 2016 2 commits
  4. 05 Feb, 2016 2 commits
  5. 31 Jan, 2016 3 commits
  6. 30 Jan, 2016 1 commit
  7. 29 Jan, 2016 4 commits
  8. 28 Jan, 2016 1 commit
  9. 26 Jan, 2016 6 commits
  10. 25 Jan, 2016 9 commits
    • antirez's avatar
      Fix merge issues with 3.2 backports. · 72f53260
      antirez authored
      72f53260
    • antirez's avatar
      Redis 3.0.7. · 53c9c299
      antirez authored
      53c9c299
    • antirez's avatar
      Minor MIGRATE refactoring. · d4090b16
      antirez authored
      Centralize cleanup of newargv in a single place.
      Add more comments to help a bit following a complex function.
      
      Related to issue #3016.
      d4090b16
    • antirez's avatar
      More variadic MIGRATE fixes. · 29c89df4
      antirez authored
      Another leak was fixed in the case of syntax error by restructuring the
      allocation strategy for the two dynamic vectors.
      
      We also make sure to always close the cached socket on I/O errors so that
      all the I/O errors are handled the same, even if we had a previously
      queued error of a different kind from the destination server.
      
      Thanks to Kevin McGehee. Related to issue #3016.
      29c89df4
    • antirez's avatar
      Various fixes to MIGRATE with multiple keys. · 14e15996
      antirez authored
      In issue #3016 Kevin McGehee identified multiple very serious issues in
      the new implementation of MIGRATE. This commit attempts to restructure
      the code in oder to avoid mistakes, an analysis of the new
      implementation is in progress in order to check for possible edge cases.
      14e15996
    • antirez's avatar
      Test: Handle LOADING in restart_instance. · 4300a973
      antirez authored
      4300a973
    • antirez's avatar
      5a402ce2
    • antirez's avatar
      Cluster: fix setting nodes slaveof pointer to NULL on node release. · 515392c2
      antirez authored
      With this commit we preserve the list of nodes that have .slaveof set
      to the node, even when the node is turned into a slave, and make sure to
      fix the .slaveof pointers to NULL when a node is freed from memory,
      regardless of the fact it's a slave or a master.
      
      Basically we try to remember the logical master in the current
      configuration even if the logical master advertised it as a slave
      already. However we still remember the associations, so that when a node
      is freed we can fix them.
      
      This should fix issue #3002.
      515392c2
    • antirez's avatar
      Cluster: clarify node->slave may be NULL. · d5872e8e
      antirez authored
      d5872e8e