- 09 May, 2020 1 commit
-
-
antirez authored
We want to send pings and pongs at specific intervals, since our packets also contain information about the configuration of the cluster and are used for gossip. However since our cluster bus is used in a mixed way for data (such as Pub/Sub or modules cluster messages) and metadata, sometimes a very busy channel may delay the reception of pong packets. So after discussing it in #7216, this commit introduces a new field that is not exposed in the cluster, is only an internal information about the last time we received any data from a given node: we use this field in order to avoid detecting failures, claiming data reception of new data from the node is a proof of liveness.
-
- 06 May, 2020 6 commits
-
-
antirez authored
-
Salvatore Sanfilippo authored
Remove unreachable branch.
-
Salvatore Sanfilippo authored
add jemalloc-bg-thread config in redis conf
-
Salvatore Sanfilippo authored
add include guard for lolwut.h
-
hwware authored
-
hwware authored
-
- 05 May, 2020 13 commits
-
-
Salvatore Sanfilippo authored
redis-cli cluster reshard does not work with ACL (AUTH2 MIGRATE args un-implemented)
-
Brad Dunbar authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
Salvatore Sanfilippo authored
make struct user anonymous (only typedefed) in server.h
-
Titouan Christophe authored
This works because this struct is never referenced by its name, but always by its type. This prevents a conflict with struct user from <sys/user.h> when compiling against uclibc. Signed-off-by:
Titouan Christophe <titouan.christophe@railnova.eu>
-
Salvatore Sanfilippo authored
Add --user argument to redis-benchmark.c (ACL)
-
antirez authored
-
Salvatore Sanfilippo authored
Fixed compiler warnings on rev(ulong) function
-
antirez authored
-
antirez authored
-
- 04 May, 2020 14 commits
-
-
Benjamin Sergeant authored
-
Muhammad Zahalqa authored
-
antirez authored
-
antirez authored
See #7188.
-
Salvatore Sanfilippo authored
Client Side Caching: Add Number of Tracking Prefix Stats in Server Info
-
antirez authored
-
antirez authored
-
Salvatore Sanfilippo authored
Support setcpuaffinity on linux/bsd
-
Salvatore Sanfilippo authored
XPENDING should not update consumer's seen-time
-
Guy Benoish authored
Same goes for XGROUP DELCONSUMER (But in this case, it doesn't have any visible effect)
-
Salvatore Sanfilippo authored
optimize memory usage of deferred replies - fixed
-
Salvatore Sanfilippo authored
reformat code
-
Salvatore Sanfilippo authored
add daily github actions with libc malloc and valgrind, fix leaks and timing issues
-
Oran Agra authored
* fix memlry leaks with diskless replica short read. * fix a few timing issues with valgrind runs * fix issue with valgrind and watchdog schedule signal about the valgrind WD issue: the stack trace test in logging.tcl, has issues with valgrind: ==28808== Can't extend stack to 0x1ffeffdb38 during signal delivery for thread 1: ==28808== too small or bad protection modes it seems to be some valgrind bug with SA_ONSTACK. SA_ONSTACK seems unneeded since WD is not recursive (SA_NODEFER was removed), also, not sure if it's even valid without a call to sigaltstack()
-
- 03 May, 2020 1 commit
-
-
Deliang Yang authored
-
- 02 May, 2020 4 commits
-
-
hwware authored
-
zhenwei pi authored
Currently, there are several types of threads/child processes of a redis server. Sometimes we need deeply optimise the performance of redis, so we would like to isolate threads/processes. There were some discussion about cpu affinity cases in the issue: https://github.com/antirez/redis/issues/2863 So implement cpu affinity setting by redis.conf in this patch, then we can config server_cpulist/bio_cpulist/aof_rewrite_cpulist/ bgsave_cpulist by cpu list. Examples of cpulist in redis.conf: server_cpulist 0-7:2 means cpu affinity 0,2,4,6 bio_cpulist 1,3 means cpu affinity 1,3 aof_rewrite_cpulist 8-11 means cpu affinity 8,9,10,11 bgsave_cpulist 1,10-11 means cpu affinity 1,10,11 Test on linux/freebsd, both work fine. Signed-off-by:
zhenwei pi <pizhenwei@bytedance.com>
-
Oran Agra authored
When deffered reply is added the previous reply node cannot be used so all the extra space we allocated in it is wasted. in case someone uses deffered replies in a loop, each time adding a small reply, each of these reply nodes (the small string reply) would have consumed a 16k block. now when we add anther diferred reply node, we trim the unused portion of the previous reply block. see #7123 cherry picked from commit fb732f7a with fix to handle a crash with LIBC allocator, which apparently can return the same pointer despite changing it's size. i.e. shrinking an allocation of 16k into 56 bytes without changing the pointer.
-
Benjamin Sergeant authored
-
- 01 May, 2020 1 commit
-
-
antirez authored
We could use uint64_t specific macros, but after all it's simpler to just use an obvious equivalent type plus casting: this will be a no op and is simpler than fixed size types printf macros.
-