1. 20 Mar, 2012 1 commit
  2. 19 Mar, 2012 3 commits
  3. 18 Mar, 2012 4 commits
  4. 16 Mar, 2012 3 commits
  5. 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
  6. 14 Mar, 2012 4 commits
  7. 13 Mar, 2012 7 commits
  8. 10 Mar, 2012 10 commits
  9. 09 Mar, 2012 1 commit
  10. 08 Mar, 2012 4 commits
  11. 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