1. 30 Aug, 2018 2 commits
    • antirez's avatar
      While the slave is busy, just accumulate master input. · e8d35809
      antirez authored
      Processing command from the master while the slave is in busy state is
      not correct, however we cannot, also, just reply -BUSY to the
      replication stream commands from the master. The correct solution is to
      stop processing data from the master, but just accumulate the stream
      into the buffers and resume the processing later.
      
      Related to #5297.
      e8d35809
    • antirez's avatar
      Allow scripts to timeout even if from the master instance. · 4b68dbcb
      antirez authored
      However the master scripts will be impossible to kill.
      
      Related to #5297.
      4b68dbcb
  2. 29 Aug, 2018 7 commits
  3. 27 Aug, 2018 8 commits
  4. 26 Aug, 2018 6 commits
  5. 25 Aug, 2018 1 commit
  6. 23 Aug, 2018 1 commit
    • zhaozhao.zz's avatar
      networking: make setProtocolError simple and clear · f2ad89a3
      zhaozhao.zz authored
      Function setProtocolError just records proctocol error
      details in server log, set client as CLIENT_CLOSE_AFTER_REPLY.
      It doesn't care about querybuf sdsrange, because we
      will do it after procotol parsing.
      f2ad89a3
  7. 21 Aug, 2018 1 commit
    • Oran Agra's avatar
      Fix unstable tests on slow machines. · c8452ab0
      Oran Agra authored
      Few tests had borderline thresholds that were adjusted.
      
      The slave buffers test had two issues, preventing the slave buffer from growing:
      1) the slave didn't necessarily go to sleep on time, or woke up too early,
         now using SIGSTOP to make sure it goes to sleep exactly when we want.
      2) the master disconnected the slave on timeout
      c8452ab0
  8. 14 Aug, 2018 4 commits
  9. 13 Aug, 2018 2 commits
  10. 03 Aug, 2018 4 commits
  11. 02 Aug, 2018 3 commits
  12. 01 Aug, 2018 1 commit
    • antirez's avatar
      Fix zslUpdateScore() edge case. · 2f282aee
      antirez authored
      When the element new score is the same of prev/next node, the
      lexicographical order kicks in, so we can safely update the node in
      place only when the new score is strictly between the adjacent nodes
      but never equal to one of them.
      
      Technically speaking we could do extra checks to make sure that even if the
      score is the same as one of the adjacent nodes, we can still update on
      place, but this rarely happens, so probably not a good deal to make it
      more complex.
      
      Related to #5179.
      2f282aee