1. 07 Mar, 2012 1 commit
  2. 29 Feb, 2012 5 commits
  3. 28 Feb, 2012 6 commits
  4. 26 Feb, 2012 4 commits
  5. 24 Feb, 2012 2 commits
  6. 23 Feb, 2012 2 commits
  7. 22 Feb, 2012 8 commits
  8. 21 Feb, 2012 5 commits
  9. 19 Feb, 2012 3 commits
  10. 16 Feb, 2012 4 commits
    • 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
    • antirez's avatar
      Issue #330 regression test. · d3473481
      antirez authored
      d3473481
    • antirez's avatar
      a400a9b2
    • antirez's avatar