VM can't suppert Lists Or sets have much numbers。 #1

tongxiaojun · 2010-01-23T08:57:47Z

VM can't suppert Lists Or sets have much numbers。

antirez · 2010-01-23T09:24:16Z

Hello,

can you please elaborate a bit? Like how much numbers, how to replicate, and the error reported by Redis. Thanks!

tongxiaojun · 2010-01-23T16:18:01Z

when I use command like redis-cli -r 10000000 lpush mylist aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa[1k content]。the redis will use a lot of memory。

tongxiaojun · 2010-01-23T16:30:34Z

redis_version:1.3.3
arch_bits:64
multiplexing_api:epoll
process_id:26560
uptime_in_seconds:106
uptime_in_days:0
connected_clients:2
connected_slaves:0
blocked_clients:0
used_memory:179048675
used_memory_human:170.75M
changes_since_last_save:559778
bgsave_in_progress:0
last_save_time:1264264099
bgrewriteaof_in_progress:0
total_connections_received:39
total_commands_processed:1181478
vm_enabled:1
role:master
vm_conf_max_memory:0
vm_conf_page_size:256
vm_conf_pages:104857600
vm_stats_used_pages:0
vm_stats_swapped_objects:0
vm_stats_swappin_count:1
vm_stats_swappout_count:1
vm_stats_io_newjobs_len:0
vm_stats_io_processing_len:0
vm_stats_io_processed_len:0
vm_stats_io_waiting_clients:0
vm_stats_io_active_threads:0
db0:keys=1,expires=0

this info show redis can't VM one key。

tongxiaojun · 2010-01-23T16:39:02Z

my redis config is vm-max-memory 0
I want use reids list pop push make a simple queue 。
but I find redis can't VM a key lists to many numbers。like 1000 0000 numbers and use a little memory。and it will use nearby 80% system memory at most。and when i run this long time 。
the linux will crash [my max system memory is 4G ]。

antirez · 2010-01-23T16:46:41Z

Hello, thanks for the info, could you please enter IRC irc.freenode.org #redis for a chat?

antirez · 2010-02-19T10:25:37Z

Can't remember the details, but this issue is now closed.

Add appendx command

## Issues and solutions from #12817 1. Touch ProcessingEventsWhileBlocked and calling moduleCount() without GIL in afterSleep() - Introduced: Version: 7.0.0 PR: #9963 - Harm Level: Very High If the module thread calls `RM_Yield()` before the main thread enters afterSleep(), and modifies `ProcessingEventsWhileBlocked`(+1), it will cause the main thread to not wait for GIL, which can lead to all kinds of unforeseen problems, including memory data corruption. - Initial / Abandoned Solution: * Added `__thread` specifier for ProcessingEventsWhileBlocked. `ProcessingEventsWhileBlocked` is used to protect against nested event processing, but event processing in the main thread and module threads should be completely independent and unaffected, so it is safer to use TLS. * Adding a cached module count to keep track of the current number of modules, to avoid having to use `dictSize()`. - Related Warnings: ``` WARNING: ThreadSanitizer: data race (pid=1136) Write of size 4 at 0x0001045990c0 by thread T4 (mutexes: write M0): #0 processEventsWhileBlocked networking.c:4135 (redis-server:arm64+0x10006d124) #1 RM_Yield module.c:2410 (redis-server:arm64+0x10018b66c) #2 bg_call_worker <null>:83232836 (blockedclient.so:arm64+0x16a8) Previous read of size 4 at 0x0001045990c0 by main thread: #0 afterSleep server.c:1861 (redis-server:arm64+0x100024f98) #1 aeProcessEvents ae.c:408 (redis-server:arm64+0x10000fd64) #2 aeMain ae.c:496 (redis-server:arm64+0x100010f0c) #3 main server.c:7220 (redis-server:arm64+0x10003f38c) ``` 2. aeApiPoll() is not thread-safe When using RM_Yield to handle events in a module thread, if the main thread has not yet entered `afterSleep()`, both the module thread and the main thread may touch `server.el` at the same time. - Introduced: Version: 7.0.0 PR: #9963 - Old / Abandoned Solution: Adding a new mutex to protect timing between after beforeSleep() and before afterSleep(). Defect: If the main thread enters the ae loop without any IO events, it will wait until the next timeout or until there is any event again, and the module thread will always hang until the main thread leaves the event loop. - Related Warnings: ``` SUMMARY: ThreadSanitizer: data race ae_kqueue.c:55 in addEventMask ================== ================== WARNING: ThreadSanitizer: data race (pid=14682) Write of size 4 at 0x000100b54000 by thread T9 (mutexes: write M0): #0 aeApiPoll ae_kqueue.c:175 (redis-server:arm64+0x100010588) #1 aeProcessEvents ae.c:399 (redis-server:arm64+0x10000fb84) #2 processEventsWhileBlocked networking.c:4138 (redis-server:arm64+0x10006d3c4) #3 RM_Yield module.c:2410 (redis-server:arm64+0x10018b66c) #4 bg_call_worker <null>:16042052 (blockedclient.so:arm64+0x169c) Previous write of size 4 at 0x000100b54000 by main thread: #0 aeApiPoll ae_kqueue.c:175 (redis-server:arm64+0x100010588) #1 aeProcessEvents ae.c:399 (redis-server:arm64+0x10000fb84) #2 aeMain ae.c:496 (redis-server:arm64+0x100010da8) #3 main server.c:7238 (redis-server:arm64+0x10003f51c) ``` ## The final fix as the comments: #12817 (comment) Optimized solution based on the above comment: First, we add `module_gil_acquring` to indicate whether the main thread is currently in the acquiring GIL state. When the module thread starts to yield, there are two possibilities(we assume the caller keeps the GIL): 1. The main thread is in the mid of beforeSleep() and afterSleep(), that is, `module_gil_acquring` is not 1 now. At this point, the module thread will wake up the main thread through the pipe and leave the yield, waiting for the next yield when the main thread may already in the acquiring GIL state. 2. The main thread is in the acquiring GIL state. The module thread release the GIL, yielding CPU to give the main thread an opportunity to start event processing, and then acquire the GIL again until the main thread releases it. This is what #12817 (comment) mentioned direction. --------- Co-authored-by: Oran Agra <oran@redislabs.com>

## Issues and solutions from redis#12817 1. Touch ProcessingEventsWhileBlocked and calling moduleCount() without GIL in afterSleep() - Introduced: Version: 7.0.0 PR: redis#9963 - Harm Level: Very High If the module thread calls `RM_Yield()` before the main thread enters afterSleep(), and modifies `ProcessingEventsWhileBlocked`(+1), it will cause the main thread to not wait for GIL, which can lead to all kinds of unforeseen problems, including memory data corruption. - Initial / Abandoned Solution: * Added `__thread` specifier for ProcessingEventsWhileBlocked. `ProcessingEventsWhileBlocked` is used to protect against nested event processing, but event processing in the main thread and module threads should be completely independent and unaffected, so it is safer to use TLS. * Adding a cached module count to keep track of the current number of modules, to avoid having to use `dictSize()`. - Related Warnings: ``` WARNING: ThreadSanitizer: data race (pid=1136) Write of size 4 at 0x0001045990c0 by thread T4 (mutexes: write M0): #0 processEventsWhileBlocked networking.c:4135 (redis-server:arm64+0x10006d124) redis#1 RM_Yield module.c:2410 (redis-server:arm64+0x10018b66c) redis#2 bg_call_worker <null>:83232836 (blockedclient.so:arm64+0x16a8) Previous read of size 4 at 0x0001045990c0 by main thread: #0 afterSleep server.c:1861 (redis-server:arm64+0x100024f98) redis#1 aeProcessEvents ae.c:408 (redis-server:arm64+0x10000fd64) redis#2 aeMain ae.c:496 (redis-server:arm64+0x100010f0c) redis#3 main server.c:7220 (redis-server:arm64+0x10003f38c) ``` 2. aeApiPoll() is not thread-safe When using RM_Yield to handle events in a module thread, if the main thread has not yet entered `afterSleep()`, both the module thread and the main thread may touch `server.el` at the same time. - Introduced: Version: 7.0.0 PR: redis#9963 - Old / Abandoned Solution: Adding a new mutex to protect timing between after beforeSleep() and before afterSleep(). Defect: If the main thread enters the ae loop without any IO events, it will wait until the next timeout or until there is any event again, and the module thread will always hang until the main thread leaves the event loop. - Related Warnings: ``` SUMMARY: ThreadSanitizer: data race ae_kqueue.c:55 in addEventMask ================== ================== WARNING: ThreadSanitizer: data race (pid=14682) Write of size 4 at 0x000100b54000 by thread T9 (mutexes: write M0): #0 aeApiPoll ae_kqueue.c:175 (redis-server:arm64+0x100010588) redis#1 aeProcessEvents ae.c:399 (redis-server:arm64+0x10000fb84) redis#2 processEventsWhileBlocked networking.c:4138 (redis-server:arm64+0x10006d3c4) redis#3 RM_Yield module.c:2410 (redis-server:arm64+0x10018b66c) redis#4 bg_call_worker <null>:16042052 (blockedclient.so:arm64+0x169c) Previous write of size 4 at 0x000100b54000 by main thread: #0 aeApiPoll ae_kqueue.c:175 (redis-server:arm64+0x100010588) redis#1 aeProcessEvents ae.c:399 (redis-server:arm64+0x10000fb84) redis#2 aeMain ae.c:496 (redis-server:arm64+0x100010da8) redis#3 main server.c:7238 (redis-server:arm64+0x10003f51c) ``` ## The final fix as the comments: redis#12817 (comment) Optimized solution based on the above comment: First, we add `module_gil_acquring` to indicate whether the main thread is currently in the acquiring GIL state. When the module thread starts to yield, there are two possibilities(we assume the caller keeps the GIL): 1. The main thread is in the mid of beforeSleep() and afterSleep(), that is, `module_gil_acquring` is not 1 now. At this point, the module thread will wake up the main thread through the pipe and leave the yield, waiting for the next yield when the main thread may already in the acquiring GIL state. 2. The main thread is in the acquiring GIL state. The module thread release the GIL, yielding CPU to give the main thread an opportunity to start event processing, and then acquire the GIL again until the main thread releases it. This is what redis#12817 (comment) mentioned direction. --------- Co-authored-by: Oran Agra <oran@redislabs.com>

fix some issues that come from sanitizer thread report. 1. when the main thread is updating daylight_active, other threads (bio, module thread) may be writing logs at the same time. ``` WARNING: ThreadSanitizer: data race (pid=661064) Read of size 4 at 0x55c9a4d11c70 by thread T2: #0 serverLogRaw /home/sundb/data/redis_fork/src/server.c:116 (redis-server+0x8d797) (BuildId: dca0b1945ba30010e36129bdb296e488dd2b32d0) #1 _serverLog.constprop.2 /home/sundb/data/redis_fork/src/server.c:146 (redis-server+0x2a3b14) (BuildId: dca0b1945ba30010e36129bdb296e488dd2b32d0) #2 bioProcessBackgroundJobs /home/sundb/data/redis_fork/src/bio.c:329 (redis-server+0x1c24ca) (BuildId: dca0b1945ba30010e36129bdb296e488dd2b32d0) Previous write of size 4 at 0x55c9a4d11c70 by main thread (mutexes: write M0, write M1, write M2, write M3): #0 updateCachedTimeWithUs /home/sundb/data/redis_fork/src/server.c:1102 (redis-server+0x925e7) (BuildId: dca0b1945ba30010e36129bdb296e488dd2b32d0) #1 updateCachedTimeWithUs /home/sundb/data/redis_fork/src/server.c:1087 (redis-server+0x925e7) #2 updateCachedTime /home/sundb/data/redis_fork/src/server.c:1118 (redis-server+0x925e7) #3 afterSleep /home/sundb/data/redis_fork/src/server.c:1811 (redis-server+0x925e7) #4 aeProcessEvents /home/sundb/data/redis_fork/src/ae.c:389 (redis-server+0x85ae0) (BuildId: dca0b1945ba30010e36129bdb296e488dd2b32d0) #5 aeProcessEvents /home/sundb/data/redis_fork/src/ae.c:342 (redis-server+0x85ae0) #6 aeMain /home/sundb/data/redis_fork/src/ae.c:477 (redis-server+0x85ae0) #7 main /home/sundb/data/redis_fork/src/server.c:7211 (redis-server+0x7168c) (BuildId: dca0b1945ba30010e36129bdb296e488dd2b32d0) ``` 2. thread leaks in module tests ``` WARNING: ThreadSanitizer: thread leak (pid=668683) Thread T13 (tid=670041, finished) created by main thread at: #0 pthread_create ../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:1036 (libtsan.so.2+0x3d179) (BuildId: 28a9f70061dbb2dfa2cef661d3b23aff4ea13536) #1 HelloBlockNoTracking_RedisCommand /home/sundb/data/redis_fork/tests/modules/blockonbackground.c:200 (blockonbackground.so+0x97fd) (BuildId: 9cd187906c57e88cdf896d121d1d96448b37a136) #2 HelloBlockNoTracking_RedisCommand /home/sundb/data/redis_fork/tests/modules/blockonbackground.c:169 (blockonbackground.so+0x97fd) #3 call /home/sundb/data/redis_fork/src/server.c:3546 (redis-server+0x9b7fb) (BuildId: dca0b1945ba30010e36129bdb296e488dd2b32d0) #4 processCommand /home/sundb/data/redis_fork/src/server.c:4176 (redis-server+0xa091c) (BuildId: dca0b1945ba30010e36129bdb296e488dd2b32d0) #5 processCommandAndResetClient /home/sundb/data/redis_fork/src/networking.c:2468 (redis-server+0xd2b8e) (BuildId: dca0b1945ba30010e36129bdb296e488dd2b32d0) #6 processInputBuffer /home/sundb/data/redis_fork/src/networking.c:2576 (redis-server+0xd2b8e) #7 readQueryFromClient /home/sundb/data/redis_fork/src/networking.c:2722 (redis-server+0xd358f) (BuildId: dca0b1945ba30010e36129bdb296e488dd2b32d0) #8 callHandler /home/sundb/data/redis_fork/src/connhelpers.h:58 (redis-server+0x288a7b) (BuildId: dca0b1945ba30010e36129bdb296e488dd2b32d0) #9 connSocketEventHandler /home/sundb/data/redis_fork/src/socket.c:277 (redis-server+0x288a7b) #10 aeProcessEvents /home/sundb/data/redis_fork/src/ae.c:417 (redis-server+0x85b45) (BuildId: dca0b1945ba30010e36129bdb296e488dd2b32d0) #11 aeProcessEvents /home/sundb/data/redis_fork/src/ae.c:342 (redis-server+0x85b45) #12 aeMain /home/sundb/data/redis_fork/src/ae.c:477 (redis-server+0x85b45) #13 main /home/sundb/data/redis_fork/src/server.c:7211 (redis-server+0x7168c) (BuildId: dca0b1945ba30010e36129bdb296e488dd2b32d0) ```

…IREAT commands (#13310) 1. Don't allow HEXPIRE/HEXPIREAT/HPEXPIRE/HPEXPIREAT command expire parameters is negative 2. Remove a dead code reported from Coverity. when `unit` is not `UNIT_SECONDS`, the second `if (expire > (long long) EB_EXPIRE_TIME_MAX)` will be dead code. ```c # t_hash.c 2988 /* Check expire overflow */ cond_at_most: Condition expire > 281474976710655LL, taking false branch. Now the value of expire is at most 281474976710655. 2989 if (expire > (long long) EB_EXPIRE_TIME_MAX) { 2990 addReplyErrorExpireTime(c); 2991 return; 2992 } 2994 if (unit == UNIT_SECONDS) { 2995 if (expire > (long long) EB_EXPIRE_TIME_MAX / 1000) { 2996 addReplyErrorExpireTime(c); 2997 return; 2998 } 2999 expire *= 1000; 3000 } else { at_most: At condition expire > 281474976710655LL, the value of expire must be at most 281474976710655. dead_error_condition: The condition expire > 281474976710655LL cannot be true. 3001 if (expire > (long long) EB_EXPIRE_TIME_MAX) { CID 494223: (#1 of 1): Logically dead code (DEADCODE) dead_error_begin: Execution cannot reach this statement: addReplyErrorExpireTime(c);. 3002 addReplyErrorExpireTime(c); 3003 return; 3004 } 3005 } ``` --------- Co-authored-by: Ozan Tezcan <ozantezcan@gmail.com>

…ytes struct to 64 Bytes): reduces LLC misses and Memory Loads (#13296) The following PR goes from 33 cacheline on getKeysResult struct (by default has 256 static buffer) ``` root@hpe10:~/redis# pahole -p ./src/server.o -C getKeysResult typedef struct { keyReference keysbuf[256]; /* 0 2048 */ /* --- cacheline 32 boundary (2048 bytes) --- */ /* typedef keyReference */ struct { int pos; int flags; } *keys; /* 2048 8 */ int numkeys; /* 2056 4 */ int size; /* 2060 4 */ /* size: 2064, cachelines: 33, members: 4 */ /* last cacheline: 16 bytes */ } getKeysResult; ``` to 1 cacheline with a static buffer of 6 keys per command): ``` root@hpe10:~/redis# pahole -p ./src/server.o -C getKeysResult typedef struct { int numkeys; /* 0 4 */ int size; /* 4 4 */ keyReference keysbuf[6]; /* 8 48 */ /* typedef keyReference */ struct { int pos; int flags; } *keys; /* 56 8 */ /* size: 64, cachelines: 1, members: 4 */ } getKeysResult; ``` we get around 1.5% higher ops/sec, and a confirmation of around 15% less LLC loads on getNodeByQuery and 37% less Stores. Function / Call Stack | CPU Time: Difference | CPU Time: 9462436 | CPU Time: this PR | Loads: Difference | Loads: 9462436 | Loads: this PR | Stores: Difference | Stores: 9462436 | Stores: This PR -- | -- | -- | -- | -- | -- | -- | -- | -- | -- getNodeByQuery | 0.753767 | 1.57118 | 0.817416 | 144297829 (15% less loads) | 920575969 | 776278140 | 367607824 (37% less stores) | 991642384 | 624034560 ## results on client side ### baseline ``` taskset -c 2,3 memtier_benchmark -s 192.168.1.200 --port 6379 --authenticate perf --cluster-mode --pipeline 10 --data-size 100 --ratio 1:0 --key-pattern P:P --key-minimum=1 --key-maximum 1000000 --test-time 180 -c 25 -t 2 --hide-histogram Writing results to stdout [RUN #1] Preparing benchmark client... [RUN #1] Launching threads now... [RUN #1 100%, 180 secs] 0 threads: 110333450 ops, 604992 (avg: 612942) ops/sec, 84.75MB/sec (avg: 85.86MB/sec), 0.82 (avg: 0.81) msec latency 2 Threads 25 Connections per thread 180 Seconds ALL STATS ====================================================================================================================================================== Type Ops/sec Hits/sec Misses/sec MOVED/sec ASK/sec Avg. Latency p50 Latency p99 Latency p99.9 Latency KB/sec ------------------------------------------------------------------------------------------------------------------------------------------------------ Sets 612942.14 --- --- 0.00 0.00 0.81332 0.80700 1.26300 2.92700 87924.12 Gets 0.00 0.00 0.00 0.00 0.00 --- --- --- --- 0.00 Waits 0.00 --- --- --- --- --- --- --- --- --- Totals 612942.14 0.00 0.00 0.00 0.00 0.81332 0.80700 1.26300 2.92700 87924.12 ``` ### comparison ``` taskset -c 2,3 memtier_benchmark -s 192.168.1.200 --port 6379 --authenticate perf --cluster-mode --pipeline 10 --data-size 100 --ratio 1:0 --key-pattern P:P --key-minimum=1 --key-maximum 1000000 --test-time 180 -c 25 -t 2 --hide-histogram Writing results to stdout [RUN #1] Preparing benchmark client... [RUN #1] Launching threads now... [RUN #1 100%, 180 secs] 0 threads: 111731310 ops, 610195 (avg: 620707) ops/sec, 85.48MB/sec (avg: 86.95MB/sec), 0.82 (avg: 0.80) msec latency 2 Threads 25 Connections per thread 180 Seconds ALL STATS ====================================================================================================================================================== Type Ops/sec Hits/sec Misses/sec MOVED/sec ASK/sec Avg. Latency p50 Latency p99 Latency p99.9 Latency KB/sec ------------------------------------------------------------------------------------------------------------------------------------------------------ Sets 620707.72 --- --- 0.00 0.00 0.80312 0.79900 1.23900 2.87900 89037.78 Gets 0.00 0.00 0.00 0.00 0.00 --- --- --- --- 0.00 Waits 0.00 --- --- --- --- --- --- --- --- --- Totals 620707.72 0.00 0.00 0.00 0.00 0.80312 0.79900 1.23900 2.87900 89037.78 ``` Co-authored-by: filipecosta90 <filipecosta.90@gmail.com>

antirez mentioned this issue Jan 12, 2012

Crash with ASSERTION FAILED after longer uptime #243

Closed

sujithrs mentioned this issue Feb 29, 2012

make test Redis did not closed connection after protocol desync #325

Closed

jinzongna mentioned this issue Mar 12, 2012

Got crash on the first run #375

Closed

gofish mentioned this issue Mar 14, 2012

Fix signal handler #213

Closed

evilpacket mentioned this issue Apr 5, 2012

2.6 Denial of Service via EVAL loadfile() #436

Closed

daxelrod mentioned this issue May 6, 2012

Inconsistent results from 'make test' for 2.6.0-rc3 #501

Closed

rbucker mentioned this issue May 7, 2012

gmake test #498

Closed

donzell mentioned this issue May 23, 2012

redis 99% cpu when master down #518

Closed

agentzh mentioned this issue Jul 2, 2012

Segfaults of redis-2.6.0-rc5 on Linux x86_64 #572

Closed

crowdstarops mentioned this issue Jul 23, 2012

redis 2.4.4 master crash #598

Closed

sanghvidk mentioned this issue Sep 25, 2012

redis hangs on realloc and after that becomes unusable #687

Closed

mahengyang mentioned this issue Oct 23, 2012

redis-2.6.0/src/replication.c:381: undefined reference to `sync_file_range' #721

Closed

mezzatto mentioned this issue Nov 5, 2012

Error compiling branch 2.6 in RHEL5 with 32bit mode #753

Closed

charsyam mentioned this issue Nov 14, 2012

I would like to know the correct condition of "maxmemory reach". #763

Closed

bzadhere mentioned this issue Nov 22, 2012

redis 2.6.4 install also fail? #785

Closed

ghost mentioned this issue Jan 7, 2013

problem happended in case of migrating key using redis cluster version #863

Closed

antirez added a commit that referenced this issue Jan 8, 2013

PSYNC: work in progress, preview #1

6f6ba62

bjne mentioned this issue Jan 22, 2013

lua struct.unpack redis segfault #901

Closed

stamhe mentioned this issue Feb 27, 2013

set proctitle #973

Closed

AllenDou mentioned this issue Mar 12, 2013

Segmentation fault in redis-cli with --bigkeys #989

Closed

liguirong98 mentioned this issue Mar 28, 2013

CentOs make redis2.6.11 error #1027

Closed

lonchura mentioned this issue Apr 5, 2013

[exception]: Executing test client: assertion:Server started even if RDB was unreadable! #1034

Closed

Cloven mentioned this issue May 6, 2013

pub/sub race condition as designed currently? #1089

Closed

anoakie referenced this issue in anoakie/redis May 17, 2013

Merge pull request StumbleUponArchive#1 from anoakie/unstable

8cf1f06

Add appendx command

This was referenced Nov 14, 2023

Redis did not save neither regularly nor on server reboot, one month of data lost #3000

Closed

[BUG] redis did not load dump.rdb after restart - all data lost #12762

Open

rajendra-dendukuri mentioned this issue Nov 15, 2023

[CRASH] Redis 6.0.6 crash with SIGILL in processMultibulkBuffer #12071

Open

rishinair19 mentioned this issue Nov 20, 2023

[CRASH] Redis crashing on 7.2.3 version #12785

Closed

slkbnt mentioned this issue Nov 22, 2023

[BUG] Debain 12: make test [exception]: Executing test client: permission denied. #12792

Closed

beovideskevin mentioned this issue Nov 24, 2023

[CRASH] My Redis server is crashing. Im on a Mac Book Pro, M2, using docker #12806

Open

kiyyer1 mentioned this issue Dec 5, 2023

SIGSEGV Guru Meditation: "Unknown sorted set encoding" #t_zset.c:961 seen in Redis 2.8.4 #12831

Closed

bluebiubluebiu mentioned this issue Jan 19, 2024

[CRASH] Redis 5.0.7 assertion failure 'dictFind(db->dict,key->ptr) != NULL' #12967

Open

opser-gavin mentioned this issue Feb 1, 2024

[CRASH] Crashed running the instuction at: 0x4b4377 #13019

Closed

bkienker mentioned this issue Feb 19, 2024

[BUG] Replica Sentinels become unresponsive shortly after startup #13034

Closed

wangbin77 mentioned this issue Mar 14, 2024

[CRASH] Redis 6.2.7 crashed by signal: 11, si_code: 128 #13137

Open

moticless mentioned this issue Mar 26, 2024

Hash Field Expiration - Draft #13172

Merged

WhiteChan18 mentioned this issue Apr 8, 2024

[BUG]Redis Fail to Start #13198

Closed

doxg mentioned this issue Apr 11, 2024

[CRASH] Redis 7.2.4 crashed by signal: 6, si_code: -6 #13203

Open

SarthakSahu mentioned this issue Apr 12, 2024

[CRASH] Redis 7.2.3 crashed in slotToKeyReplaceEntry #13205

Closed

more456 mentioned this issue Apr 15, 2024

[BUG] - Server Keeps crashing randomly #13213

Open

SarthakSahu mentioned this issue May 3, 2024

[CRASH] Redis 7.0.12 crashed in zsetDel #13247

Open

un99known99 mentioned this issue May 19, 2024

new version 7.2.5 not offered to be upgraded #13280

Closed

moticless mentioned this issue Jun 24, 2024

Fix H(P)EXPIREAT command to propagate HDEL as well #13364

Merged

noris-spfab mentioned this issue Jun 26, 2024

[CRASH] redis in a 3-node replication setup crashed. #13368

Closed

yanxianhe mentioned this issue Aug 17, 2024

[CRASH] <short description> #13477

Closed

Kevin-zhao326 mentioned this issue Aug 29, 2024

[CRASH] <short description>Redis 6.2.7 crashed by signal: 11 #13475

Open

a296961081 mentioned this issue Sep 13, 2024

Restarting the slave node redis, an error occurred when importing rdb #13544

Open

adihegde23 mentioned this issue Sep 16, 2024

[CRASH] Redis seems to be crashing while creating RDB. #13552

Open

moticless mentioned this issue Sep 22, 2024

Fix race in HFE tests #13563

Merged

This issue was closed.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

VM can't suppert Lists Or sets have much numbers。 #1

VM can't suppert Lists Or sets have much numbers。 #1

tongxiaojun commented Jan 23, 2010

antirez commented Jan 23, 2010

tongxiaojun commented Jan 23, 2010

tongxiaojun commented Jan 23, 2010

tongxiaojun commented Jan 23, 2010

antirez commented Jan 23, 2010

antirez commented Feb 19, 2010

VM can't suppert Lists Or sets have much numbers。 #1

VM can't suppert Lists Or sets have much numbers。 #1

Comments

tongxiaojun commented Jan 23, 2010

antirez commented Jan 23, 2010

tongxiaojun commented Jan 23, 2010

tongxiaojun commented Jan 23, 2010

tongxiaojun commented Jan 23, 2010

antirez commented Jan 23, 2010

antirez commented Feb 19, 2010