- 11 Dec, 2018 1 commit
-
-
Salvatore Sanfilippo authored
Cluster manager fix cmd
-
- 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 12 commits
-
-
Salvatore Sanfilippo authored
remove useless tryObjectEncoding in debug assert
-
Salvatore Sanfilippo authored
fix #5580, display fragmentation and rss overhead bytes as signed
-
antirez authored
-
antirez authored
-
Salvatore Sanfilippo authored
networking: current_client should not be NULL when trim qb_pos
-
antirez authored
-
antirez authored
-
Salvatore Sanfilippo authored
redis-cli reshard/rebalance: ability to force replacement on existing keys
-
zhaozhao.zz authored
-
yura authored
-
Salvatore Sanfilippo authored
cli: pass auth through REDISCLI_AUTH
-
Salvatore Sanfilippo authored
Fix cluster call reply format readable
-
- 04 Dec, 2018 3 commits
-
-
Salvatore Sanfilippo authored
Fixed a serverPanic when sending an invalid command to a monitor client
-
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 12 commits
-
-
Salvatore Sanfilippo authored
fix small test suite race conditions
-
Salvatore Sanfilippo authored
MEMORY command: make USAGE more accurate
-
Salvatore Sanfilippo authored
Fix choose a random master node for slot assignment
-
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.
-
Salvatore Sanfilippo authored
fix comment typo in util.c
-
antirez authored
-
Qu Chen authored
-
Salvatore Sanfilippo authored
Clarify the "Creating Server TCP listening socket" error message
-
Salvatore Sanfilippo authored
Don't treat unsupported protocols as fatal errors
-
Salvatore Sanfilippo authored
Backtrace/register dump on BSD.
-
Salvatore Sanfilippo authored
Don't call sdscmp() with shared.maxstring or shared.minstring
-
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 2 commits
-
-
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>.
-
Chris Lamb authored
This really helps spot it in the logs, otherwise it does not look like a warning/error. For example: Creating Server TCP listening socket ::1:6379: bind: Cannot assign requested address ... is not nearly as clear as: Could not create server TCP listening listening socket ::1:6379: bind: Cannot assign requested address
-