1. 04 Mar, 2014 8 commits
    • Matt Stancliff's avatar
      Bind source address for cluster communication · e5b1e7be
      Matt Stancliff authored
      The first address specified as a bind parameter
      (server.bindaddr[0]) gets used as the source IP
      for cluster communication.
      
      If no bind address is specified by the user, the
      behavior is unchanged.
      
      This patch allows multiple Redis Cluster instances
      to communicate when running on the same interface
      of the same host.
      e5b1e7be
    • antirez's avatar
      Sentinel test: set less time sensitive defaults. · 8d011492
      antirez authored
      This commit sets the failover timeout to 30 seconds instead of the 180
      seconds default, and allows to reconfigure multiple slaves at the same
      time.
      
      This makes tests less sensible to timing, with the result that there are
      less false positives due to normal behaviors that require time to
      succeed or to be retried.
      
      However the long term solution is probably some way in order to detect
      when a test failed because of timing issues (for example split brain
      during leader election) and retry it.
      8d011492
    • antirez's avatar
      Sentinel: more aggressive failover start desynchronization. · 47750998
      antirez authored
      Sentinel needs to avoid split brain conditions due to multiple sentinels
      trying to get voted at the exact same time.
      
      So far some desynchronization was provided by fluctuating server.hz,
      that is the frequency of the timer function call. However the
      desynchonization provided in this way was not enough when using many
      Sentinel instances, especially when a large quorum value is used in
      order to force a greater degree of agreement (more than N/2+1).
      
      It was verified that it was likely to trigger a split brain
      condition, forcing the system to try again after a timeout.
      Usually the system will succeed after a few retries, but this is not
      optimal.
      
      This commit desynchronizes instances in a more effective way to make it
      likely that the first attempt will be successful.
      47750998
    • antirez's avatar
      08da025f
    • antirez's avatar
      Sentinel test: debugging console improved. · efb092ba
      antirez authored
      efb092ba
    • antirez's avatar
      Sentinel test: initial debugging console. · 7d97a4c9
      antirez authored
      7d97a4c9
    • antirez's avatar
    • antirez's avatar
      Sentiel test: add test start time in output. · dd8d883c
      antirez authored
      dd8d883c
  2. 03 Mar, 2014 10 commits
  3. 28 Feb, 2014 2 commits
    • Matt Stancliff's avatar
      Force INFO used_memory_peak to match peak memory · f1c9a203
      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.)
      f1c9a203
    • antirez's avatar
      Sentinel test: Makefile target added. · a89c8bb8
      antirez authored
      a89c8bb8
  4. 27 Feb, 2014 10 commits
    • michael-grunder's avatar
      Improved bigkeys with progress, pipelining and summary · 806788d0
      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
      806788d0
    • antirez's avatar
      BITPOS fuzzy testing. · 8b8c1cd4
      antirez authored
      8b8c1cd4
    • antirez's avatar
      Basic BITPOS tests. · b21f4d63
      antirez authored
      b21f4d63
    • antirez's avatar
      warnigns -> warnings in redisBitpos(). · 76a6e82d
      antirez authored
      76a6e82d
    • antirez's avatar
      More consistent BITPOS behavior with bit=0 and ranges. · 0e31eaa2
      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.
      0e31eaa2
    • antirez's avatar
      Initial implementation of BITPOS. · 38c620b3
      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.
      38c620b3
    • antirez's avatar
    • antirez's avatar
      8d95a474
    • antirez's avatar
      BITCOUNT fuzzy test with random start/end added. · 2a7847a3
      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.
      2a7847a3
    • antirez's avatar
      Fix misaligned word access in redisPopcount(). · 746ce35f
      antirez authored
      746ce35f
  5. 25 Feb, 2014 10 commits