1. 13 Feb, 2018 3 commits
    • Guy Benoish's avatar
      rewriteAppendOnlyFileBackground() failure fix · f7820067
      Guy Benoish authored
      It is possible to do BGREWRITEAOF even if appendonly=no. This is by design.
      stopAppendonly() didn't turn off aof_rewrite_scheduled (it can be turned on
      again by BGREWRITEAOF even while appendonly is off anyway).
      After configuring `appendonly yes` it will see that the state is AOF_OFF,
      there's no RDB fork, so it will do rewriteAppendOnlyFileBackground() which
      will fail since the aof_child_pid is set (was scheduled and started by cron).
      
      Solution:
      stopAppendonly() will turn off the schedule flag (regardless of who asked for it).
      startAppendonly() will terminate any existing fork and start a new one (so it is the most recent).
      f7820067
    • Salvatore Sanfilippo's avatar
      Merge pull request #4684 from oranagra/latency_monitor_max · 480d4af1
      Salvatore Sanfilippo authored
      fix to latency monitor reporting wrong max latency
      480d4af1
    • Oran Agra's avatar
      fix to latency monitor reporting wrong max latency · 8e8d957f
      Oran Agra authored
      in some cases LATENCY HISTORY reported latency that was
      higher than the max latency reported by LATENCY LATEST / DOCTOR
      8e8d957f
  2. 02 Feb, 2018 1 commit
  3. 24 Jan, 2018 3 commits
  4. 23 Jan, 2018 1 commit
  5. 18 Jan, 2018 3 commits
    • antirez's avatar
      727dd436
    • Guy Benoish's avatar
      Replication buffer fills up on high rate traffic. · fd8efb7c
      Guy Benoish authored
      When feeding the master with a high rate traffic the the slave's feed is much slower.
      This causes the replication buffer to grow (indefinitely) which leads to slave disconnection.
      The problem is that writeToClient() decides to stop writing after NET_MAX_WRITES_PER_EVENT
      writes (In order to be fair to clients).
      We should ignore this when the client is a slave.
      It's better if clients wait longer, the alternative is that the slave has no chance to stay in
      sync in this situation.
      fd8efb7c
    • antirez's avatar
      Cluster: improve anti-affinity algo in redis-trib.rb. · 1673a3f3
      antirez authored
      See #3462 and related PRs.
      
      We use a simple algorithm to calculate the level of affinity violation,
      and then an optimizer that performs random swaps until things improve.
      1673a3f3
  6. 17 Jan, 2018 4 commits
  7. 16 Jan, 2018 4 commits
  8. 15 Jan, 2018 3 commits
  9. 14 Jan, 2018 1 commit
  10. 12 Jan, 2018 5 commits
  11. 11 Jan, 2018 4 commits
  12. 09 Jan, 2018 4 commits
  13. 07 Jan, 2018 1 commit
  14. 05 Jan, 2018 2 commits
  15. 03 Jan, 2018 1 commit