API/RPC sometimes does not respond

[huglester]

RPC server sometimes does not respond. example:

# while true; do curl --request POST 'http://127.0.0.1:8545' --header 'Content-Type: application/json' --data-raw '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":83}'; sleep 1; done
{"jsonrpc":"2.0","id":83,"result":"0x557a924"}
{"jsonrpc":"2.0","id":83,"result":"0x557a924"}
curl: (56) Recv failure: Connection reset by peer
{"jsonrpc":"2.0","id":83,"result":"0x557a924"}
{"jsonrpc":"2.0","id":83,"result":"0x557a924"}
{"jsonrpc":"2.0","id":83,"result":"0x557a924"}
curl: (56) Recv failure: Connection reset by peer
{"jsonrpc":"2.0","id":83,"result":"0x557a924"}
curl: (56) Recv failure: Connection reset by peer
{"jsonrpc":"2.0","id":83,"result":"0x557a924"}
{"jsonrpc":"2.0","id":83,"result":"0x557a924"}
{"jsonrpc":"2.0","id":83,"result":"0x557a924"}
{"jsonrpc":"2.0","id":83,"result":"0x557a924"}
{"jsonrpc":"2.0","id":83,"result":"0x557a924"}
{"jsonrpc":"2.0","id":83,"result":"0x557a924"}
curl: (56) Recv failure: Connection reset by peer
curl: (56) Recv failure: Connection reset by peer
curl: (56) Recv failure: Connection reset by peer
curl: (56) Recv failure: Connection reset by peer
curl: (56) Recv failure: Connection reset by peer
{"jsonrpc":"2.0","id":83,"result":"0x557a979"}
curl: (56) Recv failure: Connection reset by peer
curl: (56) Recv failure: Connection reset by peer
curl: (56) Recv failure: Connection reset by peer
curl: (56) Recv failure: Connection reset by peer
curl: (56) Recv failure: Connection reset by peer
curl: (56) Recv failure: Connection reset by peer
{"jsonrpc":"2.0","id":83,"result":"0x557a9a5"}
curl: (56) Recv failure: Connection reset by peer
{"jsonrpc":"2.0","id":83,"result":"0x557a9a5"}
{"jsonrpc":"2.0","id":83,"result":"0x557a9a5"}
curl: (56) Recv failure: Connection reset by peer
curl: (56) Recv failure: Connection reset by peer
curl: (56) Recv failure: Connection reset by peer
curl: (56) Recv failure: Connection reset by peer
{"jsonrpc":"2.0","id":83,"result":"0x557a9a5"}
{"jsonrpc":"2.0","id":83,"result":"0x557a9a5"}
curl: (56) Recv failure: Connection reset by peer
{"jsonrpc":"2.0","id":83,"result":"0x557a9fe"}
{"jsonrpc":"2.0","id":83,"result":"0x557a9fe"}
{"jsonrpc":"2.0","id":83,"result":"0x557a9fe"}
curl: (56) Recv failure: Connection reset by peer
{"jsonrpc":"2.0","id":83,"result":"0x557a9fe"}
{"jsonrpc":"2.0","id":83,"result":"0x557a9fe"}
{"jsonrpc":"2.0","id":83,"result":"0x557a9fe"}
{"jsonrpc":"2.0","id":83,"result":"0x557a9fe"}
{"jsonrpc":"2.0","id":83,"result":"0x557a9fe"}
{"jsonrpc":"2.0","id":83,"result":"0x557a9fe"}
{"jsonrpc":"2.0","id":83,"result":"0x557a9fe"}
curl: (56) Recv failure: Connection reset by peer
{"jsonrpc":"2.0","id":83,"result":"0x557a9fe"}

It might be probably due to I see in logs: "INFO [04-12|21:39:30.029] Deep froze chain segment" I have 2x NVMe disks in raid0, so disks are not the issue here It is an archive node.

is there anything what can be done improved? Some hidden tricks?

[Chomtana]

Stale pre-bedrock issue