Engine API: NewPayload fails with a "context canceled" error when calling CurrentHeader/GetHeader #9786
Description
System information
Erigon version: 2.59.0-0f0a4452
OS & Version: ubuntu-jammy-22.04
Erigon Command (with flags/config): erigon --db.size.limit=8TB --chain=mainnet --datadir=/opt/data/erigon --authrpc.addr=0.0.0.0 --authrpc.vhosts=* --authrpc.port=8551 --authrpc.jwtsecret=/engine.jwt --prune=default --ws --http --http.vhosts=* --http.corsdomain=* --http.addr=0.0.0.0 --http.port=8545 --http.api=engine,net,eth,web3,debug,trace --metrics --metrics.addr=0.0.0.0 --metrics.port=6060 --torrent.download.rate=512mb
Consensus Layer: Prysm v.5.0.1
Consensus Layer Command (with flags/config): beacon-chain --accept-terms-of-use=true --datadir=/opt/app/beacon --p2p-host-dns= --mainnet=true --block-batch-limit=512 --rpc-host=0.0.0.0 --grpc-gateway-host=0.0.0.0 --p2p-max-peers=100 --execution-endpoint=http://127.0.0.1:8545 --monitoring-host=0.0.0.0 --monitoring-port=8080 --p2p-tcp-port=13001 --p2p-udp-port=12001 --jwt-secret=/engine.jwt
Chain/Network: Ethereum Mainnet
Actual behaviour
After we upgraded our archive erigon node from 2.58.2 to 2.59.0, we have a database issue that we didn't have with the previous version. Our applications that are using rpc/ws endpoints of the node, are now causing the following logs at the node:
Also sometimes rpc requests are ending with 'context canceled' error:
[rpc] served conn=127.0.0.1:60950 method=eth_getLogs reqid=4 t=37.440560913s err="context canceled"
When the node is not used for rpc requests, everything works fine. We think it is related with some performance issue caused by the new version