1. 13 Apr, 2012 2 commits
    • antirez's avatar
      Stop access to global vars. Not configurable. · 97cab309
      antirez authored
      After considering the interaction between ability to delcare globals in
      scripts using the 'global' function, and the complexities related to
      hanlding replication and AOF in a sane way with globals AND ability to
      turn protection On and Off, we reconsidered the design. The new design
      makes clear that there is only one good way to write Redis scripts, that
      is not using globals. In the rare cases state must be retained across
      calls a Redis key can be used.
      97cab309
    • antirez's avatar
      3e6a4463
  2. 10 Apr, 2012 1 commit
  3. 28 Mar, 2012 1 commit
  4. 25 Mar, 2012 2 commits
    • antirez's avatar
      CONFIG RESETSTAT resets two more fields. · d0407c2d
      antirez authored
      d0407c2d
    • antirez's avatar
      New INFO field aof_delayed_fsync introduced. · 81f32c7b
      antirez authored
      This new field counts all the times Redis is configured with AOF enabled and
      fsync policy 'everysec', but the previous fsync performed by the
      background thread was not able to complete within two seconds, forcing
      Redis to perform a write against the AOF file while the fsync is still
      in progress (likely a blocking operation).
      81f32c7b
  5. 22 Mar, 2012 1 commit
    • antirez's avatar
      Support for read-only slaves. Semantical fixes. · 05406168
      antirez authored
      This commit introduces support for read only slaves via redis.conf and CONFIG GET/SET commands. Also various semantical fixes are implemented here:
      
      1) MULTI/EXEC with only read commands now work where the server is into a state where writes (or commands increasing memory usage) are not allowed. Before this patch everything inside a transaction would fail in this conditions.
      
      2) Scripts just calling read-only commands will work against read only
      slaves, when the server is out of memory, or when persistence is into an
      error condition. Before the patch EVAL always failed in this condition.
      05406168
  6. 10 Mar, 2012 2 commits
  7. 08 Mar, 2012 1 commit
  8. 07 Mar, 2012 1 commit
    • antirez's avatar
      By default Redis refuses writes with an error if the latest BGSAVE failed (and... · 4d3bbf35
      antirez authored
      By default Redis refuses writes with an error if the latest BGSAVE failed (and at least one save point is configured). However people having good monitoring systems may prefer a server that continues to work, since they are notified that there are problems by their monitoring systems. This commit implements the ability to turn the feature on or off via redis.conf and CONFIG SET.
      4d3bbf35
  9. 24 Jan, 2012 1 commit
  10. 16 Jan, 2012 1 commit
  11. 03 Jan, 2012 1 commit
  12. 21 Dec, 2011 4 commits
  13. 01 Dec, 2011 1 commit
  14. 31 Oct, 2011 2 commits
  15. 26 Oct, 2011 1 commit
  16. 10 Oct, 2011 1 commit
  17. 05 Oct, 2011 1 commit
  18. 04 Oct, 2011 1 commit
  19. 27 Jul, 2011 1 commit
  20. 12 Jul, 2011 1 commit
  21. 30 Jun, 2011 1 commit
  22. 25 Jun, 2011 1 commit
  23. 10 Jun, 2011 3 commits
  24. 25 May, 2011 1 commit
  25. 07 Apr, 2011 1 commit
  26. 29 Mar, 2011 1 commit
  27. 09 Mar, 2011 1 commit
  28. 22 Feb, 2011 1 commit
  29. 21 Feb, 2011 1 commit
  30. 17 Feb, 2011 1 commit
  31. 14 Feb, 2011 1 commit