1. 28 Feb, 2014 1 commit
    • 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
  2. 27 Feb, 2014 9 commits
  3. 25 Feb, 2014 17 commits
  4. 24 Feb, 2014 7 commits
  5. 23 Feb, 2014 4 commits
  6. 22 Feb, 2014 2 commits
    • antirez's avatar
      Sentinel: IDONTKNOW error removed. · b1c13863
      antirez authored
      This error was conceived for the older version of Sentinel that worked
      via master redirection and that was not able to get configuration
      updates from other Sentinels via the Pub/Sub channel of masters or
      slaves.
      
      This reply does not make sense today, every Sentinel should reply with
      the best information it has currently. The error will make even more
      sense in the future since the plan is to allow Sentinels to update the
      configuration of other Sentinels via gossip with a direct chat without
      the prerequisite that they have at least a monitored instance in common.
      b1c13863
    • antirez's avatar
      Sentinel test: framework improved and conf-update unit added. · 8c254415
      antirez authored
      It is now possible to kill and restart sentinel or redis instances for
      more real-world testing.
      
      The 01 unit tests the capability of Sentinel to update the configuration
      of Sentinels rejoining the cluster, however the test is pretty trivial
      and more tests should be added.
      8c254415