1. 22 Feb, 2012 2 commits
  2. 21 Feb, 2012 9 commits
  3. 20 Feb, 2012 1 commit
  4. 16 Feb, 2012 2 commits
  5. 15 Feb, 2012 10 commits
  6. 14 Feb, 2012 2 commits
  7. 02 Feb, 2012 5 commits
  8. 16 Jan, 2012 1 commit
  9. 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
  10. 12 Jan, 2012 2 commits
  11. 11 Jan, 2012 2 commits
  12. 10 Jan, 2012 1 commit
  13. 07 Jan, 2012 2 commits