1. 31 Dec, 2018 1 commit
  2. 19 Dec, 2018 1 commit
  3. 18 Dec, 2018 2 commits
    • artix's avatar
      cc295901
    • artix's avatar
      Cluster Manager: compare key values after BUSYKEY error (migration). · 143bfa1e
      artix authored
      If a key exists in the target node during a migration (BUSYKEY),
      the value of the key on both nodes (source and target) will be compared.
      If the key has the same value on both keys, the migration will be
      automatically retried with the REPLACE argument in order to override
      the target's key.
      
      If the key has different values, the behaviour will depend on such
      cases:
      - In case of 'fix' command, the migration will stop and the user
        will be warned to manually check the key(s).
      - In other cases (ie. reshard), if the user launched the command
        with the --cluster-replace option, the migration will be
        retried with the REPLACE argument, elsewhere the migration will
        stop and the user will be warned.
      143bfa1e
  4. 12 Dec, 2018 2 commits
  5. 11 Dec, 2018 7 commits
  6. 10 Dec, 2018 6 commits
  7. 07 Dec, 2018 5 commits
  8. 06 Dec, 2018 1 commit
  9. 05 Dec, 2018 1 commit
  10. 04 Dec, 2018 2 commits
  11. 02 Dec, 2018 1 commit
  12. 30 Nov, 2018 1 commit
  13. 28 Nov, 2018 2 commits
  14. 25 Nov, 2018 2 commits
  15. 23 Nov, 2018 4 commits
  16. 21 Nov, 2018 1 commit
  17. 19 Nov, 2018 1 commit
    • antirez's avatar
      Stream: fix XREADGROUP history reading of deleted messages. · 2bd6802f
      antirez authored
      This commit fixes #5570. It is a similar bug to one fixed a few weeks
      ago and is due to the range API to be called with NULL as "end ID"
      parameter instead of repeating again the start ID, to be sure that we
      selectively issue the entry with a given ID, or we get zero returned
      (and we know we should emit a NULL reply).
      2bd6802f