Skip to content
This repository has been archived by the owner on Oct 28, 2023. It is now read-only.

db-server crash under heavy load with redis-benchmark #28

Closed
ogoudron opened this issue Feb 17, 2012 · 6 comments
Closed

db-server crash under heavy load with redis-benchmark #28

ogoudron opened this issue Feb 17, 2012 · 6 comments

Comments

@ogoudron
Copy link
Contributor

I use the last version of redis-benchmark.

This is the command used to crash db-server :
./redis-benchmark -t set,get -n 1000000 -d 1024 -r 1000000 -l

After 2 or 3 loop, db-server crash.

Bests regards, Olivier Goudron

@BohuTANG
Copy link
Owner

Hi,can you give the core dump backstack info, i am away from my laptop.
Thanks

@ogoudron
Copy link
Contributor Author

Program received signal SIGSEGV, Segmentation fault.
0x0805114e in level_set_head (level=0x805a130, n=0x0) at engine/level.c:26
26 n->pre = NULL;
(gdb) bt
#0 0x0805114e in level_set_head (level=0x805a130, n=0x0) at engine/level.c:26
#1 0x080516af in _llru_set_node (lru=0x805a100, n=0xe28f978) at engine/llru.c:59
#2 0x0805197e in llru_get (lru=0x805a100, sk=0xbfff7934) at engine/llru.c:127
#3 0x0804f32b in db_get (db=0x8057028, sk=0xbfff7934, sv=0xbfff793c) at engine/db.c:45
#4 0x08049ab2 in read_handler (el=0xb097b00c, fd=169, privdata=0x0, mask=1)
at server/db-server.c:230
#5 0x0804b039 in aeProcessEvents (eventLoop=0xb097b00c, flags=3) at server/ae.c:339
#6 0x0804b33c in aeMain (eventLoop=0xb097b00c) at server/ae.c:384
#7 0x0804a348 in main () at server/db-server.c:384
(gdb)

@BohuTANG
Copy link
Owner

Hi,ogoudron

Fixup,this push commit is :debb721

But I found memory-leak in 'db-server',debug and try to fix it.

Thanks
BohuTANG

@BohuTANG BohuTANG reopened this Feb 18, 2012
@BohuTANG
Copy link
Owner

Hey,again
Fixed the memory leak when db-get, get the codes again from 'unstable' branch pls.

Thanks.
BohuTANG

@ogoudron
Copy link
Contributor Author

Thanks again for your reactivity, i will test it today.

@BohuTANG
Copy link
Owner

If you don't want to data recovery(if server crash) , change to IS_LOG_RECOVERY (0) in 'db-server.c', this is fast for performance.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants