- 09 Jan, 2019 28 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
- 06 Jan, 2019 1 commit
-
-
chenyangyang authored
Update comment
-
- 27 Dec, 2018 1 commit
-
-
artix authored
See issue #5687
-
- 19 Dec, 2018 1 commit
-
-
artix authored
-
- 18 Dec, 2018 2 commits
-
-
artix authored
-
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.
-
- 12 Dec, 2018 2 commits
- 11 Dec, 2018 5 commits
-
-
antirez authored
See #5663.
-
zhaozhao.zz authored
When loading data, we call processEventsWhileBlocked to process events and execute commands. But if we are loading AOF it's dangerous, because processCommand would call freeMemoryIfNeeded to evict, and that will break data consistency, see issue #5686.
-
antirez authored
Verified to be able to trigger at least #5632. Does not report other issues.
-
antirez authored
See #5632.
-
zhaozhao.zz authored
-