1. 12 Jun, 2018 5 commits
  2. 11 Jun, 2018 11 commits
  3. 10 Jun, 2018 3 commits
  4. 09 Jun, 2018 1 commit
  5. 08 Jun, 2018 5 commits
  6. 07 Jun, 2018 9 commits
  7. 06 Jun, 2018 2 commits
  8. 05 Jun, 2018 2 commits
  9. 04 Jun, 2018 2 commits
    • antirez's avatar
    • antirez's avatar
      XGROUP SETID implemented + consumer groups core fixes. · 36b392a0
      antirez authored
      Now that we have SETID, the inetrnals of consumer groups should be able
      to handle the case of the same message delivered multiple times just
      as a side effect of calling XREADGROUP. Normally this should never
      happen but if the admin manually "XGROUP SETID mykey mygroup 0",
      messages will get re-delivered to clients waiting for the ">" special
      ID. The consumer groups internals were not able to handle the case of a
      message re-delivered in this circumstances that was already assigned to
      another owner.
      36b392a0