1. 13 Apr, 2012 2 commits
  2. 29 Mar, 2012 3 commits
  3. 28 Mar, 2012 3 commits
  4. 27 Mar, 2012 10 commits
  5. 25 Mar, 2012 2 commits
    • antirez's avatar
      CONFIG RESETSTAT resets two more fields. · ca09ad4d
      antirez authored
      ca09ad4d
    • antirez's avatar
      New INFO field aof_delayed_fsync introduced. · c1d01b3c
      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).
      c1d01b3c
  6. 24 Mar, 2012 1 commit
  7. 23 Mar, 2012 3 commits
  8. 22 Mar, 2012 2 commits
  9. 21 Mar, 2012 1 commit
  10. 20 Mar, 2012 2 commits
    • antirez's avatar
      DEBUG should not be flagged as w otherwise we can not call DEBUG DIGEST and... · 7dcdd281
      antirez authored
      DEBUG should not be flagged as w otherwise we can not call DEBUG DIGEST and other commands against read only slaves.
      7dcdd281
    • antirez's avatar
      Support for read-only slaves. Semantical fixes. · f3fd419f
      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.
      f3fd419f
  11. 19 Mar, 2012 3 commits
  12. 18 Mar, 2012 4 commits
  13. 16 Mar, 2012 3 commits
  14. 15 Mar, 2012 1 commit
    • antirez's avatar
      Fix for issue #391. · c9d3dda2
      antirez authored
      Use a simple protocol between clientsCron() and helper functions to
      understand if the client is still valind and clientsCron() should
      continue processing or if the client was freed and we should continue
      with the next one.
      c9d3dda2