| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Related to #5145.
Design note: clients may change type when they turn into replicas or are
moved into the Pub/Sub category and so forth. Moreover the recomputation
of the bytes used is problematic for obvious reasons: it changes
continuously, so as a conservative way to avoid accumulating errors,
each client remembers the contribution it gave to the sum, and removes
it when it is freed or before updating it with the new memory usage.
|
|\
| |
| | |
fix comments about RESIZE DB opcode in rdb.c
|
| |
| |
| | |
fix comments about RESIZE DB opcode in rdb.c
|
| | |
|
|\ \
| |/
|/| |
lazyfree: add a new configuration lazyfree-lazy-user-del
|
| |
| |
| |
| |
| | |
Delete keys in async way when executing DEL command, if
lazyfree-lazy-user-del is yes.
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Initially they needed to be at the end so that we could extend to N
strings in the future, but after further consideration I no longer
believe it's worth it.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Check OOM at script start to get stable lua OOM state.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Checking OOM by `getMaxMemoryState` inside script might get different result
with `freeMemoryIfNeededAndSafe` at script start, because lua stack and
arguments also consume memory.
This leads to memory `borderline` when memory grows near server.maxmemory:
- `freeMemoryIfNeededAndSafe` at script start detects no OOM, no memory freed
- `getMaxMemoryState` inside script detects OOM, script aborted
We solve this 'borderline' issue by saving OOM state at script start to get
stable lua OOM state.
related to issue #6565 and #5250.
|
|\ \ \ \
| | | | |
| | | | | |
diffrent fix for runtest --host --port
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Try to fix time-sensitive tests in blockonkey.tcl
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
There is an inherent race between the deferring client and the
"main" client of the test: While the deferring client issues a blocking
command, we can't know for sure that by the time the "main" client
tries to issue another command (Usually one that unblocks the deferring
client) the deferring client is even blocked...
For lack of a better choice this commit uses TCL's 'after' in order
to give some time for the deferring client to issues its blocking
command before the "main" client does its thing.
This problem probably exists in many other tests but this commit
tries to fix blockonkeys.tcl
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Use __attribute__ only if __GNUC__ is defined
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Modules: Perform printf-like format checks in variadic API
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
XREAD and XREADGROUP should not be allowed from scripts when BLOCK op…
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
being used
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Stale replica should allow MULTI/EXEC
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Example: Client uses a pipe to send the following to a
stale replica:
MULTI
.. do something ...
DISCARD
The replica will reply the MUTLI with -MASTERDOWN and
execute the rest of the commands... A client using a
pipe might not be aware that MULTI failed until it's
too late.
I can't think of a reason why MULTI/EXEC/DISCARD should
not be executed on stale replicas...
Also, enable MULTI/EXEC/DISCARD during loading
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
fix integer overflow
|
| | |_|/ / / /
| |/| | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Fix no-negative-zero test
|
| |/ / / / / / |
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
modules don't signalModifiedKey in setKey() since that's done (optionally) in RM_CloseKey
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
in RM_CloseKey
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
change CI to build and run the module api tests
|
| | | | | | | | |
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
fix possible warning on incomplete struct init
|
| | | | | | | | | |
|
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
Make sure Redis does not reply with negative zero
|
| | | | | | | | | | |
|
|\ \ \ \ \ \ \ \ \ \
| |_|_|_|_|/ / / / /
|/| | | | | | | | | |
DEBUG OBJECT should pass keyname to module when loading
|
| | | | | | | | | | |
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
debug, dump registers on arm too.
|
| | | | | | | | | | | |
|