1. 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
  2. 21 Dec, 2011 2 commits
  3. 12 Nov, 2011 1 commit
  4. 09 Nov, 2011 3 commits
  5. 08 Nov, 2011 1 commit
  6. 23 Oct, 2011 1 commit
  7. 14 Oct, 2011 1 commit
  8. 04 Oct, 2011 1 commit
  9. 22 Sep, 2011 1 commit
  10. 25 Jun, 2011 1 commit
  11. 20 Jun, 2011 1 commit
  12. 17 Jun, 2011 1 commit
  13. 10 Jun, 2011 2 commits
  14. 29 May, 2011 1 commit
  15. 14 May, 2011 2 commits
  16. 13 May, 2011 3 commits
  17. 10 May, 2011 1 commit
  18. 06 Apr, 2011 3 commits
  19. 29 Mar, 2011 1 commit
  20. 10 Mar, 2011 1 commit
  21. 09 Mar, 2011 1 commit
  22. 28 Feb, 2011 7 commits
  23. 11 Feb, 2011 1 commit
  24. 07 Jan, 2011 2 commits