- 09 Jan, 2019 4 commits
- 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 7 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
-
zhaozhao.zz authored
-
antirez authored
Thanks to @soloestoy for discovering this issue in #5667. This is an alternative fix in order to avoid both cycling the clients and also disconnecting clients just having valid read-only transactions pending.
-
- 10 Dec, 2018 6 commits
-
-
artix authored
- Multiple owners checking in 'fix'/'check' commands is now optional (using --cluster-search-multiple-owners). - Updated help.
-
artix authored
- FixOpenSlot now correctly updates in-memory cluster configuration. - Improved output messages.
-
artix authored
in one node and importing state in multiple nodes.
-
artix authored
in 'fix' command.
-
artix authored
-
artix authored
all slots are covered and not open.
-
- 07 Dec, 2018 5 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
zhaozhao.zz authored
-
yura authored
-
- 06 Dec, 2018 1 commit
-
-
lsytj0413 authored
-
- 05 Dec, 2018 1 commit
-
-
hdmg authored
-
- 04 Dec, 2018 2 commits
-
-
yongman authored
-
Madelyn Olson authored
-
- 02 Dec, 2018 1 commit
-
-
Oran Agra authored
these metrics become negative when RSS is smaller than the used_memory. This can easily happen when the program allocated a lot of memory and haven't written to it yet, in which case the kernel doesn't allocate any pages to the process
-
- 30 Nov, 2018 1 commit
-
-
zhaozhao.zz authored
-
- 28 Nov, 2018 2 commits
-
-
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.
-
antirez authored
See #5612.
-
- 25 Nov, 2018 2 commits
-
-
David Carlier authored
Special treatment here as backtrace support is optional, cannot be found via pkg-config and similar neither.
-
David Carlier authored
FreeBSD/DragonFlyBSD does have backtrace only it does not belong to libc.
-
- 23 Nov, 2018 1 commit
-
-
Chris Lamb authored
If we encounter an unsupported protocol in the "bind" list, don't ipso-facto consider it a fatal error. We continue to abort startup if there are no listening sockets at all. This ensures that the lack of IPv6 support does not prevent Redis from starting on Debian where we try to bind to the ::1 interface by default (via "bind 127.0.0.1 ::1"). A machine with IPv6 disabled (such as some container systems) would simply fail to start Redis after the initiall call to apt(8). This is similar to the case for where "bind" is not specified: https://github.com/antirez/redis/issues/3894 ... and was based on the corresponding PR: https://github.com/antirez/redis/pull/4108 ... but also adds EADDRNOTAVAIL to the list of errors to catch which I believe is missing from there. This issue was raised in Debian as both <https://bugs.debian.org/900284> & <https://bugs.debian.org/914354>.
-