1. 05 Mar, 2014 4 commits
    • antirez's avatar
      Document why we update peak memory in INFO. · 1d9eb47f
      antirez authored
      1d9eb47f
    • antirez's avatar
      Fix configEpoch assignment when a cluster slot gets "closed". · e4833ed8
      antirez authored
      This is still code to rework in order to use agreement to obtain a new
      configEpoch when a slot is migrated, however this commit handles the
      special case that happens when the nodes are just started and everybody
      has a configEpoch of 0. In this special condition to have the maximum
      configEpoch is not enough as the special epoch 0 is not unique (all the
      others are).
      
      This does not fixes the intrinsic race condition of a failover happening
      while we are resharding, that will be addressed later.
      e4833ed8
    • Matt Stancliff's avatar
      Force INFO used_memory_peak to match peak memory · 7c092b67
      Matt Stancliff authored
      used_memory_peak only updates in serverCron every server.hz,
      but Redis can use more memory and a user can request memory
      INFO before used_memory_peak gets updated in the next
      cron run.
      
      This patch updates used_memory_peak to the current
      memory usage if the current memory usage is higher
      than the recorded used_memory_peak value.
      
      (And it only calls zmalloc_used_memory() once instead of
      twice as it was doing before.)
      7c092b67
    • michael-grunder's avatar
      Improved bigkeys with progress, pipelining and summary · 23addbb5
      michael-grunder authored
      This commit reworks the redis-cli --bigkeys command to provide more
      information about our progress as well as output summary information
      when we're done.
      
       - We now show an approximate percentage completion as we go
       - Hiredis pipelining is used for TYPE and SIZE retreival
       - A summary of keyspace distribution and overall breakout at the end
      23addbb5
  2. 28 Feb, 2014 1 commit
  3. 27 Feb, 2014 9 commits
    • antirez's avatar
      BITPOS fuzzy testing. · 32db37c3
      antirez authored
      32db37c3
    • antirez's avatar
      Basic BITPOS tests. · 1d62f833
      antirez authored
      1d62f833
    • antirez's avatar
      warnigns -> warnings in redisBitpos(). · 9104f1e6
      antirez authored
      9104f1e6
    • antirez's avatar
      More consistent BITPOS behavior with bit=0 and ranges. · eacc0951
      antirez authored
      With the new behavior it is possible to specify just the start in the
      range (the end will be assumed to be the first byte), or it is possible
      to specify both start and end.
      
      This is useful to change the behavior of the command when looking for
      zeros inside a string.
      
      1) If the user specifies both start and end, and no 0 is found inside
         the range, the command returns -1.
      
      2) If instead no range is specified, or just the start is given, even
         if in the actual string no 0 bit is found, the command returns the
         first bit on the right after the end of the string.
      
      So for example if the string stored at key foo is "\xff\xff":
      
          BITPOS foo (returns 16)
          BITPOS foo 0 -1 (returns -1)
          BITPOS foo 0 (returns 16)
      
      The idea is that when no end is given the user is just looking for the
      first bit that is zero and can be set to 1 with SETBIT, as it is
      "available". Instead when a specific range is given, we just look for a
      zero within the boundaries of the range.
      eacc0951
    • antirez's avatar
      Initial implementation of BITPOS. · 1f8005ca
      antirez authored
      It appears to work but more stress testing, and both unit tests and
      fuzzy testing, is needed in order to ensure the implementation is sane.
      1f8005ca
    • antirez's avatar
      cbeaf173
    • antirez's avatar
      BITCOUNT fuzzy test with random start/end added. · 9c206cc8
      antirez authored
      It was verified in practice that this test is able to stress much more
      the implementation by introducing errors that were only trivially to
      detect with different offsets but impossible to detect starting always
      at zero and counting bits the full length of the string.
      9c206cc8
    • antirez's avatar
      Fix misaligned word access in redisPopcount(). · 24265edb
      antirez authored
      24265edb
    • Matt Stancliff's avatar
      7e274194
  4. 25 Feb, 2014 26 commits