1. 02 Feb, 2012 4 commits
  2. 16 Jan, 2012 1 commit
  3. 14 Jan, 2012 1 commit
    • Pieter Noordhuis's avatar
      Don't expire keys when loading an RDB after a SYNC · aa794ac0
      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.
      aa794ac0
  4. 12 Jan, 2012 2 commits
  5. 11 Jan, 2012 2 commits
  6. 10 Jan, 2012 1 commit
  7. 07 Jan, 2012 7 commits
  8. 23 Dec, 2011 3 commits
  9. 20 Dec, 2011 3 commits
  10. 19 Dec, 2011 3 commits
  11. 18 Dec, 2011 1 commit
  12. 01 Dec, 2011 1 commit
  13. 30 Nov, 2011 2 commits
  14. 28 Nov, 2011 2 commits
  15. 25 Nov, 2011 6 commits
  16. 24 Nov, 2011 1 commit