1. 09 Jan, 2019 8 commits
  2. 06 Jan, 2019 1 commit
  3. 27 Dec, 2018 1 commit
  4. 19 Dec, 2018 1 commit
  5. 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
  6. 12 Dec, 2018 2 commits
  7. 11 Dec, 2018 7 commits
  8. 10 Dec, 2018 6 commits
  9. 07 Dec, 2018 5 commits
  10. 06 Dec, 2018 1 commit
  11. 05 Dec, 2018 1 commit
  12. 04 Dec, 2018 2 commits
  13. 02 Dec, 2018 1 commit
  14. 30 Nov, 2018 1 commit
  15. 28 Nov, 2018 1 commit
    • zhaozhao.zz's avatar
      MEMORY command: make USAGE more accurate · d56c6313
      zhaozhao.zz authored
      In MEMORY USAGE command, we count the key argv[2] into usage,
      but the argument in command may contains free spaces because of
      sdsMakeRoomFor. But the key in db never contains free spaces
      because we use sdsdup when dbAdd, so using the real key to
      count the usage is more accurate.
      d56c6313