1. 20 Mar, 2019 1 commit
  2. 18 Mar, 2019 2 commits
  3. 16 Mar, 2019 1 commit
  4. 15 Mar, 2019 3 commits
  5. 14 Mar, 2019 4 commits
  6. 13 Mar, 2019 2 commits
  7. 12 Mar, 2019 4 commits
  8. 11 Mar, 2019 1 commit
  9. 10 Mar, 2019 2 commits
  10. 09 Mar, 2019 1 commit
  11. 08 Mar, 2019 2 commits
    • Steve Webster's avatar
      Increment delivery counter on XCLAIM unless RETRYCOUNT specified · f1e7df4b
      Steve Webster authored
      The XCLAIM docs state the XCLAIM increments the delivery counter for
      messages. This PR makes the code match the documentation - which seems
      like the desired behaviour - whilst still allowing RETRYCOUNT to be
      specified manually.
      
      My understanding of the way streamPropagateXCLAIM() works is that this
      change will safely propagate to replicas since retry count is pulled
      directly from the streamNACK struct.
      
      Fixes #5194
      f1e7df4b
    • artix's avatar
      Redis Benchmark: handle CLUSTERDOWN error · 8fadebfc
      artix authored
      8fadebfc
  12. 07 Mar, 2019 5 commits
  13. 06 Mar, 2019 1 commit
  14. 05 Mar, 2019 1 commit
  15. 04 Mar, 2019 1 commit
  16. 03 Mar, 2019 1 commit
  17. 02 Mar, 2019 1 commit
    • antirez's avatar
      Use the RDB info fields to provide info to users. · b9b140e2
      antirez authored
      Fix #5790 and 5878.
      
      Maybe a better option was to have such fields named with the first
      byte '%' as those are info fields for specification, however now to
      break it in a backward incompatible way is not an option, so let's use
      the fields actively to provide info when sensible, otherwise ignore
      when they are not really helpful.
      b9b140e2
  18. 01 Mar, 2019 7 commits