Bug: In multi-threaded situations, due to incorrect initialization sequence, pika role and cmdstat_map may sometimes be incorrect #2235
Comments
chengyu-l
pushed a commit
to chengyu-l/pika
that referenced
this issue
Jan 6, 2024
chengyu-l
pushed a commit
to chengyu-l/pika
that referenced
this issue
Jan 6, 2024
KKorpse
pushed a commit
to KKorpse/pika
that referenced
this issue
Jan 11, 2024
…OpenAtomFoundation#2235) (OpenAtomFoundation#2278) Co-authored-by: liuchengyu <liuchengyu@360.cn>
bigdaronlee163
pushed a commit
to bigdaronlee163/pika
that referenced
this issue
Jun 8, 2024
…OpenAtomFoundation#2235) (OpenAtomFoundation#2278) Co-authored-by: liuchengyu <liuchengyu@360.cn>
cheniujh
pushed a commit
to cheniujh/pika
that referenced
this issue
Sep 24, 2024
…OpenAtomFoundation#2235) (OpenAtomFoundation#2278) Co-authored-by: liuchengyu <liuchengyu@360.cn>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a regression?
Yes
Description
The initialization of pika role and cmdstat_map are placed after the PikaDispatchThread and PikaClientProcessor threads have started, which in extreme cases may cause Redis command execution errors requested by the client. Because the execution order of the main thread, PikaDispatchThread thread, and PikaClientProcessor thread is uncertain. It is possible that PikaDispatchThread and PikaClientProcessor have already received a client request and start to execute commands, the initialization of pika role and cmdstat in the main thread has not been executed yet.
Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos
No response
Please provide the version you discovered this bug in (check about page for version information)
Anything else?
No response
The text was updated successfully, but these errors were encountered: