1. 02 May, 2012 1 commit
  2. 27 Apr, 2012 1 commit
    • antirez's avatar
      Don't use an alternative stack for SIGSEGV & co. · a28ab2a9
      antirez authored
      This commit reverts most of c5757662, in
      order to use back main stack for signal handling.
      
      The main reason is that otherwise it is completely pointless that we do
      a lot of efforts to print the stack trace on crash, and the content of
      the stack and registers as well. Using an alternate stack broken this
      feature completely.
      a28ab2a9
  3. 19 Apr, 2012 1 commit
  4. 18 Apr, 2012 1 commit
  5. 13 Apr, 2012 3 commits
  6. 10 Apr, 2012 2 commits
  7. 08 Apr, 2012 1 commit
  8. 06 Apr, 2012 1 commit
  9. 05 Apr, 2012 1 commit
  10. 04 Apr, 2012 4 commits
  11. 03 Apr, 2012 1 commit
  12. 30 Mar, 2012 1 commit
  13. 28 Mar, 2012 3 commits
  14. 27 Mar, 2012 1 commit
  15. 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
  16. 24 Mar, 2012 1 commit
  17. 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
  18. 19 Mar, 2012 1 commit
  19. 18 Mar, 2012 3 commits
  20. 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
  21. 14 Mar, 2012 2 commits
  22. 13 Mar, 2012 1 commit
  23. 10 Mar, 2012 1 commit
  24. 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
  25. 07 Mar, 2012 2 commits
    • 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
    • antirez's avatar
      Refuse writes if can't persist on disk. · c25e7eaf
      antirez authored
      Redis now refuses accepting write queries if RDB persistence is
      configured, but RDB snapshots can't be generated for some reason.
      The status of the latest background save operation is now exposed
      in the INFO output as well. This fixes issue #90.
      c25e7eaf