1. 14 Feb, 2013 2 commits
  2. 05 Feb, 2013 1 commit
  3. 19 Jan, 2013 1 commit
  4. 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
  5. 12 Nov, 2012 2 commits
  6. 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
  7. 08 Nov, 2012 1 commit
  8. 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
  9. 24 Aug, 2012 1 commit
    • antirez's avatar
      Better Out of Memory handling. · 6fdc6354
      antirez authored
      The previous implementation of zmalloc.c was not able to handle out of
      memory in an application-specific way. It just logged an error on
      standard error, and aborted.
      
      The result was that in the case of an actual out of memory in Redis
      where malloc returned NULL (In Linux this actually happens under
      specific overcommit policy settings and/or with no or little swap
      configured) the error was not properly logged in the Redis log.
      
      This commit fixes this problem, fixing issue #509.
      Now the out of memory is properly reported in the Redis log and a stack
      trace is generated.
      
      The approach used is to provide a configurable out of memory handler
      to zmalloc (otherwise the default one logging the event on the
      standard output is used).
      6fdc6354
  10. 24 Apr, 2012 2 commits
  11. 10 Apr, 2012 1 commit
  12. 09 Apr, 2012 1 commit
  13. 03 Apr, 2012 2 commits
  14. 02 Apr, 2012 5 commits
  15. 01 Apr, 2012 1 commit
  16. 08 Mar, 2012 1 commit
  17. 25 Jan, 2012 3 commits
  18. 08 Nov, 2011 1 commit
  19. 23 Oct, 2011 1 commit
  20. 20 Oct, 2011 1 commit
  21. 17 Oct, 2011 3 commits
  22. 13 Oct, 2011 1 commit
  23. 07 Oct, 2011 2 commits
  24. 05 Oct, 2011 2 commits
  25. 04 Oct, 2011 1 commit