1. 31 Aug, 2018 1 commit
  2. 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
  3. 29 Aug, 2018 3 commits
  4. 27 Aug, 2018 5 commits
  5. 26 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. 14 Aug, 2018 4 commits
  8. 13 Aug, 2018 1 commit
    • zhaozhao.zz's avatar
      pipeline: do not sdsrange querybuf unless all commands processed · 14c4ddb5
      zhaozhao.zz authored
      This is an optimization for processing pipeline, we discussed a
      problem in issue #5229: clients may be paused if we apply `CLIENT
      PAUSE` command, and then querybuf may grow too large, the cost of
      memmove in sdsrange after parsing a completed command will be
      horrible. The optimization is that parsing all commands in queyrbuf
      , after that we can just call sdsrange only once.
      14c4ddb5
  9. 03 Aug, 2018 2 commits
  10. 01 Aug, 2018 6 commits
  11. 31 Jul, 2018 9 commits
  12. 30 Jul, 2018 5 commits