1. 26 Feb, 2013 2 commits
  2. 25 Feb, 2013 8 commits
  3. 22 Feb, 2013 5 commits
  4. 21 Feb, 2013 5 commits
  5. 20 Feb, 2013 3 commits
  6. 15 Feb, 2013 4 commits
  7. 14 Feb, 2013 4 commits
  8. 05 Feb, 2013 1 commit
  9. 19 Jan, 2013 1 commit
  10. 14 Nov, 2012 1 commit
    • antirez's avatar
      MIGRATE: retry one time on I/O error. · 2feef47a
      antirez authored
      Now that we cache connections, a retry attempt makes sure that the
      operation don't fail just because there is an existing connection error
      on the socket, like the other end closing the connection.
      
      Unfortunately this condition is not detectable using
      getsockopt(SO_ERROR), so the only option left is to retry.
      
      We don't retry on timeouts.
      2feef47a
  11. 12 Nov, 2012 2 commits
  12. 11 Nov, 2012 1 commit
    • antirez's avatar
      MIGRATE TCP connections caching. · e23d281e
      antirez authored
      By caching TCP connections used by MIGRATE to chat with other Redis
      instances a 5x performance improvement was measured with
      redis-benchmark against small keys.
      
      This can dramatically speedup cluster resharding and other processes
      where an high load of MIGRATE commands are used.
      e23d281e
  13. 08 Nov, 2012 1 commit
  14. 07 Nov, 2012 2 commits
    • antirez's avatar
      COPY and REPLACE options for MIGRATE. · 1237d71c
      antirez authored
      With COPY now MIGRATE does not remove the key from the source instance.
      With REPLACE it uses RESTORE REPLACE on the target host so that even if
      the key already eixsts in the target instance it will be overwritten.
      
      The options can be used together.
      1237d71c
    • antirez's avatar
      REPLACE option for RESTORE. · e5b5763f
      antirez authored
      The REPLACE option deletes an existing key with the same name (if any)
      and materializes the new one. The default behavior without RESTORE is to
      return an error if a key already exists.
      e5b5763f