pika crash on unstable branch about pika

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Title: pika crash on unstable branch

Is this a regression?

No

Description

1. Refer to readme.md in the warehouse

   Ubuntu Taking Debug Mode as an Example.
   
   sudo docker run -v /Your/Path/pika:/pika --privileged=true -it ubuntu:latest
   
   sudo docker run -v ~/data/aldxData/o/pika:/pika --privileged=true -it ubuntu:latest
   

2. Run pika service host: 172.17.0.2 port: 9221

   You have to download the compiled binary file first. wget https://github.com/OpenAtomFoundation/pika/releases/download/v3.5.4/pika-v3.5.4-ubuntu-amd64.tar.gz

   Then unzip: execute

     ./bin/pika -c ./conf/pika.conf
   

3. Quickly install redis and then use redis-cli to connect to the services provided by pika server.

----------Pika config end----------
I20240522 11:53:36.240200 31844 pika.cc:209] Server at: ../../conf/pika.conf
I20240522 11:53:36.240485 31844 net_interfaces.cc:104] Using Networker Interface: eth0
I20240522 11:53:36.240569 31844 net_interfaces.cc:148] got ip 172.17.0.2
I20240522 11:53:36.240586 31844 pika_server.cc:146] host: 172.17.0.2 port: 9221
I20240522 11:53:36.240633 31844 pika_server.cc:69] Worker queue limit is 20100
W20240522 11:53:36.240648 31844 pika_server.cc:70] 0.0.0.0
I20240522 11:53:36.241966 31844 pika_server.cc:1530] Dump file is not exist,path: ./dump/
I20240522 11:53:36.242575 31844 pika_binlog.cc:98] Binlog: Find the exist file.
I20240522 11:53:36.242624 31844 pika_binlog.cc:114] Binlog: open profile ./log/log_db0/write2file0
I20240522 11:53:36.242645 31844 pika_binlog.cc:121] Binlog: filesize is 0
I20240522 11:53:36.244874 31844 pika_db.cc:50] db0 DB Success
I20240522 11:53:36.245095 31846 pika_cache_load_thread.cc:183] PikaCacheLoadThread::ThreadMain Start
I20240522 11:53:36.247982 31844 net_util.cc:129] TimerTaskThread Starting...
I20240522 11:53:36.248243 31844 pika_server.cc:196] Pika Server going to start
I20240522 11:53:36.248268 31844 rsync_server.cc:48] start RsyncServer ...
I20240522 11:53:36.248564 31844 rsync_server.cc:59] RsyncServer started ...

I20240522 11:53:42.473748 31886 pika_dispatch_thread.cc:74] new client comming, ip: 172.17.0.2
I20240522 11:53:42.473807 31886 dispatch_thread.cc:151] accept new conn 36:172.17.0.2:41168:0
I20240522 11:53:42.473830 31886 dispatch_thread.cc:159] find worker(0), refresh the last_thread_ to 0
AddressSanitizer:DEADLYSIGNAL
================================================== ===============
================================================== ===============
==31844==ERROR: AddressSanitizer: FPE on unknown address 0x55f7ddff6f8a (pc 0x55f7ddff6f8a bp 0x7f3ee2a48380 sp 0x7f3ee2a48370 T16)
#0 0x55f7ddff6f8a in storage::SlotIndexer::GetInstanceID(unsigned int) (/pika/pika/debug/pika+0xbd9f8a) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#1 0x55f7ddfc9ec3 in storage::Storage::GetDBInstance(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&) (/pika/pika/debug/pika+ 0xbacec3) (BuildId: e6a2591ff8d4930ac58
d7402abf2f68e4470c9a2)
#2 0x55f7ddfc9d8c in storage::Storage::GetDBInstance(rocksdb::Slice const&) (/pika/pika/debug/pika+0xbacd8c) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#3 0x55f7ddfc9f1d in storage::Storage::Set(rocksdb::Slice const&, rocksdb::Slice const&) (/pika/pika/debug/pika+0xbacf1d) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#4 0x55f7ddba9300 in SetCmd::Do() (/pika/pika/debug/pika+0x78c300) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#5 0x55f7ddba9c9f in SetCmd::DoThroughDB() (/pika/pika/debug/pika+0x78cc9f) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#6 0x55f7dd9f8d79 in Cmd::DoCommand(Cmd::HintKeys const&) (/pika/pika/debug/pika+0x5dbd79) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#7 0x55f7dd9f82f7 in Cmd::InternalProcessCommand(Cmd::HintKeys const&) (/pika/pika/debug/pika+0x5db2f7) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#8 0x55f7dd9f7efb in Cmd::ProcessCommand(Cmd::HintKeys const&) (/pika/pika/debug/pika+0x5daefb) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#9 0x55f7dd9f7dec in Cmd::Execute() (/pika/pika/debug/pika+0x5dadec) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#10 0x55f7dd98e351 in PikaClientConn::DoCmd(std::vector<std::__cxx11::basic_string<char, std::char_traits, std::allocator >, std::allocator<std::__cxx11 ::basic_string<char, std::char_traits, std::allocator > > > const&, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, std::shared_ptr<std: :__cxx11::basic_string<char, std::char_traits, std::
allocator > > const&) (/pika/pika/debug/pika+0x571351) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#11 0x55f7dd9945dc in PikaClientConn::ExecRedisCmd(std::vector<std::__cxx11::basic_string<char, std::char_traits, std::allocator >, std::allocator<std::__cxx11 ::basic_string<char, std::char_t
raits, std::allocator > > > const&, std::shared_ptr<std::__cxx11::basic_string<char, std::char_traits, std::allocator > >& ) (/pika/pika/debug/pika+0x5775dc) (BuildId: e6a2591ff8d4930a
c58d7402abf2f68e4470c9a2)
#12 0x55f7dd991b26 in PikaClientConn::BatchExecRedisCmd(std::vector<std::vector<std::__cxx11::basic_string<char, std::char_traits, std::allocator >, std::allocator <std::__cxx11::basic_string<
char, std::char_traits, std::allocator > > >, std::allocator<std::vector<std::__cxx11::basic_string<char, std::char_traits, std ::allocator >, std::allocator<std::__cxx11::basic_string
<char, std::char_traits, std::allocator > > > > > const&) (/pika/pika/debug/pika+0x574b26) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#13 0x55f7dd99174e in PikaClientConn::DoBackgroundTask(void*) (/pika/pika/debug/pika+0x57474e) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#14 0x55f7de242dc7 in net::ThreadPool::runInThread() (/pika/pika/debug/pika+0xe25dc7) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#15 0x55f7de241167 in net::ThreadPool::Worker::WorkerMain(void*) (/pika/pika/debug/pika+0xe24167) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#16 0x7f3ef70a0109 in asan_thread_start ../../../../src/libsanitizer/asan/asan_interceptors.cpp:234
#17 0x7f3ef6de3a93 (/lib/x86_64-linux-gnu/libc.so.6+0x9ca93) (BuildId: 4d9090d61bf70e6b3225d583f0f08193f54670b2)
#18 0x7f3ef6e70a33 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x129a33) (BuildId: 4d9090d61bf70e6b3225d583f0f08193f54670b2)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: FPE (/pika/pika/debug/pika+0xbd9f8a) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2) in storage::SlotIndexer::GetInstanceID(unsigned int)
Thread T16 created by T0 here:
#0 0x7f3ef7135469 in pthread_create ../../../../src/libsanitizer/asan/asan_interceptors.cpp:245
#1 0x55f7de241283 in net::ThreadPool::Worker::start() (/pika/pika/debug/pika+0xe24283) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#2 0x55f7de2419db in net::ThreadPool::start_thread_pool() (/pika/pika/debug/pika+0xe249db) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#3 0x55f7dd9b840c in PikaClientProcessor::Start() (/pika/pika/debug/pika+0x59b40c) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#4 0x55f7ddd4d012 in PikaServer::Start() (/pika/pika/debug/pika+0x930012) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#5 0x55f7dd82f1bc in main (/pika/pika/debug/pika+0x4121bc) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)
#6 0x7f3ef6d711c9 (/lib/x86_64-linux-gnu/libc.so.6+0x2a1c9) (BuildId: 4d9090d61bf70e6b3225d583f0f08193f54670b2)
#7 0x7f3ef6d7128a in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x2a28a) (BuildId: 4d9090d61bf70e6b3225d583f0f08193f54670b2)
#8 0x55f7dd7a0334 in _start (/pika/pika/debug/pika+0x383334) (BuildId: e6a2591ff8d4930ac58d7402abf2f68e4470c9a2)

==31844==ABORTING

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)

No response

Anything else?

No response

[cheniujh]

你的二进制应该是自己编的最新unstable吧(v3.5.4的发版二进制不应当有addressSanitizer，也没有报错的那个调用链，那个是unstable代码才有的)，我推测你运行的二进制是自己编的unstable，但是配置文件用了v3.5.4的发版conf？
最新unstable编译出来的二进制，不能搭配v3.5.4的发版conf，请直接使用unstable的conf

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Your binary should be the latest unstable one compiled by yourself. I guess you used the v3.5.4 release conf for the configuration file?
The latest binary compiled by unstable cannot be used with the v3.5.4 release conf. Please use the unstable conf directly.

[bigdaronlee163]

It is OK. Thanks. @cheniujh

[bigdaronlee163]

It is no problem.