1. 06 Apr, 2012 1 commit
  2. 05 Apr, 2012 1 commit
  3. 04 Apr, 2012 4 commits
  4. 03 Apr, 2012 1 commit
  5. 30 Mar, 2012 1 commit
  6. 28 Mar, 2012 3 commits
  7. 27 Mar, 2012 1 commit
  8. 25 Mar, 2012 1 commit
    • 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
  9. 24 Mar, 2012 1 commit
  10. 22 Mar, 2012 3 commits
    • antirez's avatar
      Correctly create shared.oomerr as an sds string. · 3f7ad833
      antirez authored
      3f7ad833
    • antirez's avatar
      DEBUG should not be flagged as w otherwise we can not call DEBUG DIGEST and... · 38bb4522
      antirez authored
      DEBUG should not be flagged as w otherwise we can not call DEBUG DIGEST and other commands against read only slaves.
      38bb4522
    • 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
  11. 19 Mar, 2012 1 commit
  12. 18 Mar, 2012 3 commits
  13. 15 Mar, 2012 1 commit
    • antirez's avatar
      Fix for issue #391. · f1eaf572
      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.
      f1eaf572
  14. 14 Mar, 2012 2 commits
  15. 13 Mar, 2012 1 commit
  16. 10 Mar, 2012 1 commit
  17. 08 Mar, 2012 2 commits
    • antirez's avatar
      Instantaneous ops/sec figure in INFO output. · 250e7f69
      antirez authored
      250e7f69
    • 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
  18. 07 Mar, 2012 4 commits
  19. 29 Feb, 2012 1 commit
  20. 28 Feb, 2012 3 commits
    • antirez's avatar
      Better system for additional commands replication. · 78d6a22d
      antirez authored
      The new code uses a more generic data structure to describe redis operations.
      The new design allows for multiple alsoPropagate() calls within the scope of a
      single command, that is useful in different contexts. For instance there
      when there are multiple clients doing BRPOPLPUSH against the same list,
      and a variadic LPUSH is performed against this list, the blocked clients
      will both be served, and we should correctly replicate multiple LPUSH
      commands after the replication of the current command.
      78d6a22d
    • antirez's avatar
      Added a new API to replicate an additional command after the replication of... · eeb34eff
      antirez authored
      Added a new API to replicate an additional command after the replication of the currently executed command, in order to propagte the LPUSH originating from RPOPLPUSH and indirectly by BRPOPLPUSH.
      eeb34eff
    • antirez's avatar
      Added command propagation API. · ad08d059
      antirez authored
      ad08d059
  21. 07 Feb, 2012 2 commits
  22. 06 Feb, 2012 2 commits