1. 29 9月, 2014 3 次提交
  2. 26 9月, 2014 1 次提交
  3. 25 9月, 2014 1 次提交
    • A
      DEBUG POPULATE two args form implemented. · d4222e6b
      antirez 提交于
      The old DEBUG POPULATE form for automatic creation of test keys is:
      
          DEBUG POPULATE <count>
      
      Now an additional form is available:
      
          DEBUG POPULATE <count> <prefix>
      
      When prefix is not specified, it defaults to "key", so the keys are
      named incrementally from key:0 to key:<count-1>. Otherwise the specified
      prefix is used instead of "key".
      
      The command is useful in order to populate different Redis instances
      with key names guaranteed to don't collide. There are other debugging
      uses, for example it is possible to add additional N keys using a count
      of N and a random prefix at every call.
      d4222e6b
  4. 22 9月, 2014 1 次提交
  5. 20 9月, 2014 5 次提交
  6. 19 9月, 2014 3 次提交
  7. 18 9月, 2014 4 次提交
  8. 17 9月, 2014 2 次提交
  9. 16 9月, 2014 5 次提交
    • A
      Better truncated AOF loading tests. · a2c740ea
      antirez 提交于
      Now there are tests to write more data after loading a truncated AOF,
      testing that the loaded data is correct, appending more, and testing
      again.
      a2c740ea
    • A
      Seek at the end of AOF after truncate call. · 878c089e
      antirez 提交于
      It is not clear if files open in append only mode will automatically fix
      their offset after a truncate(2) operation. This commit makes sure that
      we reposition the AOF file descriptor offset at the end of the file
      after a truncated AOF is loaded and trimmed to the last valid command.
      878c089e
    • A
      On AOF end of file, truncate the AOF to last valid command. · 0ba8fe1a
      antirez 提交于
      Recently we introduced the ability to load truncated AOFs, but
      unfortuantely the support was broken since the server, after loading the
      truncated AOF, continues appending to the file that is corrupted at the
      end. The problem is fixed only in the next AOF rewrite.
      
      This commit fixes the issue by truncating the AOF to the last valid
      opcode, and aborting if it is not possible to truncate the file
      correctly.
      0ba8fe1a
    • A
      Don't propagate SAVE. · 046a00a0
      antirez 提交于
      This is a general fix (check that dirty delta is positive) but actually
      should have as the only effect fixing the SAVE propagation to
      AOF and slaves.
      046a00a0
    • A
      Cluster test: unit 09, Pub/Sub across the cluster. · b82d650a
      antirez 提交于
      b82d650a
  10. 15 9月, 2014 1 次提交
  11. 12 9月, 2014 2 次提交
    • A
      Sentinel sentinelGetLeader() top comment improved. · f5efa9bb
      antirez 提交于
      f5efa9bb
    • A
      Sentinel: fix computation of total number of votes. · f4be6f16
      antirez 提交于
      The code to check the number of voters was never updated to follow the new
      Sentinel specification, so the number of voters was computed using only
      the set of Sentinels that provided a vote.
      
      This means that there is a changing majority on partitions, even if
      usually the issue is not triggered because of the configured quorum
      check (what was broken was the other implicit check that requires anyway
      half of the known sentinels to agree in order to start a failover).
      f4be6f16
  12. 10 9月, 2014 2 次提交
  13. 09 9月, 2014 1 次提交
  14. 08 9月, 2014 7 次提交
  15. 04 9月, 2014 2 次提交