New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CRASH] Redis 7.2.3 crashed in slotToKeyReplaceEntry #13205
Comments
crash in assemble 0x0000000000144b13 <+147>: call 0x134c60 <keyHashSlot>
0x0000000000144b18 <+152>: mov 0x38(%rbp),%rdx
0x0000000000144b1c <+156>: mov %eax,%eax
0x0000000000144b1e <+158>: shl $0x4,%rax
0x0000000000144b22 <+162>: add 0x50(%rdx),%rax <- crash here unsigned int hashslot = keyHashSlot(key, sdslen(key));
clusterDictMetadata *dictmeta = dictMetadata(d);
redisDb *db = dictmeta->db;
slotToKeys *slot_to_keys = &(*db->slots_to_keys).by_slot[hashslot]; |
Thank you @sundb. |
@SarthakSahu yes, but i don't know why yet, it still need some time. |
Hi @sundb Any break through here? Our cluster has been crashed again with same stacks trace. |
@SarthakSahu sorry, since i haven't had enought time to dig into it right now, could you provide more information so I can pinpoint it quickly? Or can you reproduce it quickly? |
Same as #12677? |
@stevelipinski Yes, they are same. |
Yes: ------ CONFIG DEBUG OUTPUT ------ I believe one minor difference is that in this case, activedefrag is set from the beginning, whereas in #12677, they mention setting it on a replica. |
@stevelipinski thanks a lot, this is usefull, and I will take the time to figue out why as soon as possible. |
Hi @sundb, Do we have any intermediate update to share. |
@SarthakSahu sorry, I've tried and failed to reproduce it, can you give me more clues about your system, special configurations, etc. |
@SarthakSahu disable activedefrag until bug is fixed |
AFAIK, Frequently short leaved data has been injected. This mean frequently data is keep injected and deleted. |
@SarthakSahu did you do anything special operations with the cluster? like slot migration? |
The text was updated successfully, but these errors were encountered: