1. 25 May, 2012 1 commit
    • antirez's avatar
      Four new persistence fields in INFO. A few renamed. · 33e1db36
      antirez authored
      The 'persistence' section of INFO output now contains additional four
      fields related to RDB and AOF persistence:
      
       rdb_last_bgsave_time_sec       Duration of latest BGSAVE in sec.
       rdb_current_bgsave_time_sec    Duration of current BGSAVE in sec.
       aof_last_rewrite_time_sec      Duration of latest AOF rewrite in sec.
       aof_current_rewrite_time_sec   Duration of current AOF rewrite in sec.
      
      The 'current' fields are set to -1 if a BGSAVE / AOF rewrite is not in
      progress. The 'last' fileds are set to -1 if no previous BGSAVE / AOF
      rewrites were performed.
      
      Additionally a few fields in the persistence section were renamed for
      consistency:
      
       changes_since_last_save -> rdb_changes_since_last_save
       bgsave_in_progress -> rdb_bgsave_in_progress
       last_save_time -> rdb_last_save_time
       last_bgsave_status -> rdb_last_bgsave_status
       bgrewriteaof_in_progress -> aof_rewrite_in_progress
       bgrewriteaof_scheduled -> aof_rewrite_scheduled
      
      After the renaming, fields in the persistence section start with rdb_ or
      aof_ prefix depending on the persistence method they describe.
      The field 'loading' and related fields are not prefixed because they are
      unique for both the persistence methods.
      33e1db36
  2. 24 Apr, 2012 1 commit
  3. 10 Apr, 2012 1 commit
  4. 09 Apr, 2012 3 commits
  5. 07 Apr, 2012 4 commits
  6. 31 Mar, 2012 1 commit
  7. 23 Mar, 2012 1 commit
  8. 13 Mar, 2012 2 commits
  9. 10 Mar, 2012 1 commit
  10. 07 Mar, 2012 1 commit
    • 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
  11. 16 Feb, 2012 1 commit
    • Pieter Noordhuis's avatar
      Don't expire keys when loading an RDB after a SYNC · cb598cdd
      Pieter Noordhuis authored
      The cron is responsible for expiring keys. When keys are expired at
      load time, it is possible that the snapshot of a master node gets
      modified. This can in turn lead to inconsistencies in the data set.
      
      A more concrete example of this behavior follows. A user reported a
      slave that would show an monotonically increase input buffer length,
      shortly after completing a SYNC. Also, `INFO` output showed a single
      blocked client, which could only be the master link. Investigation
      showed that indeed the `BRPOP` command was fed by the master. This
      command can only end up in the stream of write operations when it did
      NOT block, and effectively executed `RPOP`. However, when the key
      involved in the `BRPOP` is expired BEFORE the command is executed, the
      client executing it will block. The client in this case, is the master
      link.
      cb598cdd
  12. 25 Jan, 2012 1 commit
  13. 03 Jan, 2012 1 commit
  14. 21 Dec, 2011 2 commits
  15. 12 Nov, 2011 1 commit
  16. 09 Nov, 2011 3 commits
  17. 08 Nov, 2011 1 commit
  18. 23 Oct, 2011 1 commit
  19. 14 Oct, 2011 1 commit
  20. 04 Oct, 2011 1 commit
  21. 22 Sep, 2011 1 commit
  22. 25 Jun, 2011 1 commit
  23. 20 Jun, 2011 1 commit
  24. 17 Jun, 2011 1 commit
  25. 10 Jun, 2011 2 commits
  26. 29 May, 2011 1 commit
  27. 14 May, 2011 2 commits
  28. 13 May, 2011 2 commits