1. 07 3月, 2012 3 次提交
  2. 01 3月, 2012 2 次提交
  3. 29 2月, 2012 6 次提交
  4. 28 2月, 2012 3 次提交
  5. 26 2月, 2012 3 次提交
  6. 24 2月, 2012 1 次提交
  7. 23 2月, 2012 3 次提交
  8. 22 2月, 2012 6 次提交
  9. 21 2月, 2012 1 次提交
  10. 20 2月, 2012 1 次提交
  11. 17 2月, 2012 1 次提交
    • P
      Don't expire keys when loading an RDB after a SYNC · cb598cdd
      Pieter Noordhuis 提交于
      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. 16 2月, 2012 2 次提交
  13. 15 2月, 2012 2 次提交
  14. 14 2月, 2012 4 次提交
  15. 10 2月, 2012 1 次提交
  16. 09 2月, 2012 1 次提交