1. 08 Mar, 2012 2 commits
    • antirez's avatar
      run_id added to INFO output. · 91d664d6
      antirez authored
      The Run ID is a field that identifies a single execution of the Redis
      server. It can be useful for many purposes as it makes easy to detect if
      the instance we are talking about is the same, or if it is a different
      one or was rebooted. An application of run_id will be in the partial
      synchronization of replication, where a slave may request a partial sync
      from a given offset only if it is talking with the same master. Another
      application is in failover and monitoring scripts.
      91d664d6
    • antirez's avatar
      clusterGetRandomName() generalized into getRandomHexChars() so that we can use... · 44f508f1
      antirez authored
      clusterGetRandomName() generalized into getRandomHexChars() so that we can use it for the run_id field as well.
      44f508f1
  2. 07 Mar, 2012 4 commits
  3. 29 Feb, 2012 1 commit
  4. 28 Feb, 2012 4 commits
  5. 06 Feb, 2012 1 commit
  6. 04 Feb, 2012 2 commits
    • antirez's avatar
      This fixes issue #327, is a very complex fix (unfortunately), details: · f6b32c14
      antirez authored
      1) sendReplyToClient() now no longer stops transferring data to a single
      client in the case we are out of memory (maxmemory-wise).
      
      2) in processCommand() the idea of we being out of memory is no longer
      the naive zmalloc_used_memory() > server.maxmemory. To say if we can
      accept or not write queries is up to the return value of
      freeMemoryIfNeeded(), that has full control about that.
      
      3) freeMemoryIfNeeded() now does its math without considering output
      buffers size. But at the same time it can't let the output buffers to
      put us too much outside the max memory limit, so at the same time it
      makes sure there is enough effort into delivering the output buffers to
      the slaves, calling the write handler directly.
      
      This three changes are the result of many tests, I found (partially
      empirically) that is the best way to address the problem, but maybe
      we'll find better solutions in the future.
      f6b32c14
    • antirez's avatar
      Use less memory when emitting the protocol, by using more shared objects for... · 355f8591
      antirez authored
      Use less memory when emitting the protocol, by using more shared objects for commonly emitted parts of the protocol.
      355f8591
  7. 02 Feb, 2012 2 commits
  8. 01 Feb, 2012 1 commit
    • antirez's avatar
      SORT is now more deterministic: does not accept to compare by score items that... · 2c861050
      antirez authored
      SORT is now more deterministic: does not accept to compare by score items that have scores not representing a valid double. Also items with the same score are compared lexycographically. At the same time the scripting side introduced the ability to sort the output of SORT when sort uses the BY <constant> optimization, resulting in no specific ordering. Since in this case the user may use GET, and the result of GET can be null, converted into false as Lua data type, this commit also introduces the ability to sort Lua tables containining false, only if the first (faster) attempt at using just table.sort with a single argument fails.
      2c861050
  9. 31 Jan, 2012 2 commits
  10. 24 Jan, 2012 2 commits
  11. 23 Jan, 2012 1 commit
  12. 20 Jan, 2012 2 commits
  13. 17 Jan, 2012 2 commits
  14. 12 Jan, 2012 1 commit
  15. 31 Dec, 2011 3 commits
  16. 30 Dec, 2011 1 commit
  17. 21 Dec, 2011 6 commits
  18. 15 Dec, 2011 1 commit
  19. 13 Dec, 2011 1 commit
  20. 01 Dec, 2011 1 commit