- 27 Feb, 2020 20 commits
-
-
Guy Benoish authored
-
hayashier authored
-
antirez authored
-
antirez authored
-
Itamar Haber authored
... with CSC disabled
-
antirez authored
This fixes WATCH and client side caching with keys expiring because of a synchronous access and not because of background expiring.
-
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
-
Oran Agra authored
-
- 12 Feb, 2020 20 commits
-
-
Khem Raj authored
This helps in avoiding multiple definition of this variable, its also defined globally in sds.c Signed-off-by:
Khem Raj <raj.khem@gmail.com>
-
lifubang authored
Signed-off-by:
lifubang <lifubang@acmcoder.com>
-
Seunghoon Woo authored
-
Guy Benoish authored
1. Call emptyDb even in case of diskless-load: We want modules to get the same FLUSHDB event as disk-based replication. 2. Do not fire any module events when flushing the backups array. 3. Delete redundant call to signalFlushedDb (Called from emptyDb).
-
lifubang authored
Signed-off-by:
lifubang <lifubang@acmcoder.com>
-
Guy Benoish authored
Because "keymiss" is "special" compared to the rest of the notifications (Trying not to break existing apps using the 'A' format for notifications) Also updated redis.conf and module.c docs
-
Oran Agra authored
-
Oran Agra authored
-
Yossi Gottlieb authored
-
Oran Agra authored
SELECT, and HELLO are commands that may be executed by the client as soon as it connects, there's no reason to block them, preventing the client from doing the rest of his sequence (which might just be INFO or CONFIG, etc). MONITOR, DEBUG, SLOWLOG, TIME, LASTSAVE are all non-data accessing commands, which there's no reason to block.
-
Oran Agra authored
-
Oran Agra authored
the warning condition was if usage > limit (saying it'll cause eviction or oom), but in fact the eviction and oom depends on used minus slave buffers. other than fixing the condition, i add info about the current usage and limit, which may be useful when looking at the log.
-
Oran Agra authored
currently there's no bug since the flags these functions handle are always lower than 32bit, but still better fix the type to prevent future bugs.
-
Oran Agra authored
using panic rather than exit means you get s stack trace of the code path that experianced the error, and possibly other info.
-
Oran Agra authored
this function possibly iterates on the module list
-
Oran Agra authored
-
Oran Agra authored
replicationUnsetMaster can be called from other places, not just replicaofCOmmand, and all of these need to restart AOF
-
Oran Agra authored
althouh in theory, users can do BGREWRITEAOF even if aof is disabled, i suppose it is more common that the scheduled flag is set by either startAppendOnly, of a failed initial AOFRW fork (AOF_WAIT_REWRITE)
-
Oran Agra authored
-
Oran Agra authored
-