1. 22 Nov, 2012 7 commits
    • antirez's avatar
      Redis 2.6.5 · 3ccfb5a4
      antirez authored
      3ccfb5a4
    • antirez's avatar
      EVALSHA is now case insensitive. · 9120275d
      antirez authored
      EVALSHA used to crash if the SHA1 was not lowercase (Issue #783).
      Fixed using a case insensitive dictionary type for the sha -> script
      map used for replication of scripts.
      9120275d
    • antirez's avatar
      Fix integer overflow in zunionInterGenericCommand(). · de00a5a0
      antirez authored
      This fixes issue #761.
      de00a5a0
    • antirez's avatar
      2b45ef02
    • antirez's avatar
      52bd3d8a
    • antirez's avatar
      Test: MULTI/EXEC tests moved into multi.tcl. · 37d978d9
      antirez authored
      37d978d9
    • antirez's avatar
      Safer handling of MULTI/EXEC on errors. · 41f0f927
      antirez authored
      After the transcation starts with a MULIT, the previous behavior was to
      return an error on problems such as maxmemory limit reached. But still
      to execute the transaction with the subset of queued commands on EXEC.
      
      While it is true that the client was able to check for errors
      distinguish QUEUED by an error reply, MULTI/EXEC in most client
      implementations uses pipelining for speed, so all the commands and EXEC
      are sent without caring about replies.
      
      With this change:
      
      1) EXEC fails if at least one command was not queued because of an
      error. The EXECABORT error is used.
      2) A generic error is always reported on EXEC.
      3) The client DISCARDs the MULTI state after a failed EXEC, otherwise
      pipelining multiple transactions would be basically impossible:
      After a failed EXEC the next transaction would be simply queued as
      the tail of the previous transaction.
      41f0f927
  2. 20 Nov, 2012 2 commits
    • antirez's avatar
      Children creating AOF or RDB files now report memory used by COW. · 5ab4151d
      antirez authored
      Finally Redis is able to report the amount of memory used by
      copy-on-write while saving an RDB or writing an AOF file in background.
      
      Note that this information is currently only logged (at NOTICE level)
      and not shown in INFO because this is less trivial (but surely doable
      with some minor form of interprocess communication).
      
      The reason we can't capture this information on the parent before we
      call wait3() is that the Linux kernel will release the child memory
      ASAP, and only retain the minimal state for the process that is useful
      to report the child termination to the parent.
      
      The COW size is obtained by summing all the Private_Dirty fields found
      in the "smap" file inside the proc filesystem for the process.
      
      All this is Linux specific and is not available on other systems.
      5ab4151d
    • antirez's avatar
      zmalloc_get_private_dirty() function added (Linux only). · e95ca663
      antirez authored
      For non Linux systmes it just returns 0.
      
      This function is useful to estimate copy-on-write because of childs
      saving stuff on disk.
      e95ca663
  3. 14 Nov, 2012 1 commit
  4. 12 Nov, 2012 3 commits
  5. 08 Nov, 2012 4 commits
  6. 06 Nov, 2012 1 commit
  7. 02 Nov, 2012 1 commit
  8. 01 Nov, 2012 5 commits
  9. 31 Oct, 2012 2 commits
  10. 30 Oct, 2012 2 commits
  11. 26 Oct, 2012 4 commits
  12. 25 Oct, 2012 2 commits
  13. 24 Oct, 2012 1 commit
  14. 22 Oct, 2012 5 commits
    • antirez's avatar
      Redis 2.6.0 · 5eec376c
      antirez authored
      5eec376c
    • antirez's avatar
      A filed called slave_read_only added in INFO output. · 99d7dbe6
      antirez authored
      This was an important information missing from the INFO output in the
      replication section.
      
      It obviously reflects if the slave is read only or not.
      99d7dbe6
    • Greg Hurrell's avatar
      Fix (cosmetic) typos in dict.h · a61705dd
      Greg Hurrell authored
      a61705dd
    • Schuster's avatar
      redis-check-dump now understands dumps produced by Redis 2.6 · 16144589
      Schuster authored
      (Commit message from @antirez as it was missign in the original commits,
      also the patch was modified a bit to still work with 2.4 dumps and to
      avoid if expressions that are always true due to checked types range)
      
      This commit changes redis-check-dump to account for new encodings and
      for the new MSTIME expire format. It also refactors the test for valid
      type into a function.
      
      The code is still compatible with Redis 2.4 generated dumps.
      
      This fixes issue #709.
      16144589
    • antirez's avatar
      Default memory limit for 32bit instanced moved from 3.5 GB to 3 GB. · a25b25f4
      antirez authored
      In some system, notably osx, the 3.5 GB limit was too far and not able
      to prevent a crash for out of memory. The 3 GB limit works better and it
      is still a lot of memory within a 4 GB theorical limit so it's not going
      to bore anyone :-)
      
      This fixes issue #711
      a25b25f4