Bg: storage executes ingest, rocksdb triggers write stall, storage will always report leader election failure, query storage, it will report rpc timeout
reason:GraphStorageServiceHandler, RaftexService,RaftPart shares the cpu threads pool
The first step of RaftPart's heartbeat will write rocksdb, if now rocksdb write stall
, a host has a large number of part leaders, which will cause all cpu thread pools to be blocked in write rocksdb (assuming the write stall exceeds 60s,ex:ingest), at this time storage raft will fail, and storage query will also fail
I think raftPart should be created separately without affecting the call of rpc
Bg: storage executes ingest, rocksdb triggers write stall, storage will always report leader election failure, query storage, it will report rpc timeout reason:GraphStorageServiceHandler, RaftexService,RaftPart shares the cpu threads pool
![image](https://user-images.githubusercontent.com/122794081/219998504-2a95ddbb-68ad-4904-b850-1dcc327e9e91.png)
The first step of RaftPart's heartbeat will write rocksdb, if now rocksdb write stall , a host has a large number of part leaders, which will cause all cpu thread pools to be blocked in write rocksdb (assuming the write stall exceeds 60s,ex:ingest), at this time storage raft will fail, and storage query will also fail I think raftPart should be created separately without affecting the call of rpc![image](https://user-images.githubusercontent.com/122794081/222104988-4d47268b-5048-4152-b3c6-d34b39c45926.png)