You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the restarting node may have sent out too many requests and exceeded the number of inbound_substreams and getting insta-bannded by lighthouse peers (Seeing HandlerRejected in logs):
After a restart, the beacon node would usually have to perform some block lookups to sync to the latest head, it seems like we've exceed the max number of concurrent requests allowed per peer (32 defined here)
Start local testnet with the network_params_das_local.yaml config
Stop one of the lighthouse node and restart it immediately
cd scripts/local_testnet
./start_local_testnet.sh -n ./network_params_das_local.yaml
# restart a LH node
kurtosis service stop local-testnet cl-3-lighthouse-geth
kurtosis service start local-testnet cl-3-lighthouse-geth
The text was updated successfully, but these errors were encountered:
Description
It looks like the restarting node may have sent out too many requests and exceeded the number of
inbound_substreams
and getting insta-bannded by lighthouse peers (SeeingHandlerRejected
in logs):lighthouse/beacon_node/lighthouse_network/src/rpc/handler.rs
Lines 881 to 886 in bf4cbd3
After a restart, the beacon node would usually have to perform some block lookups to sync to the latest head, it seems like we've exceed the max number of concurrent requests allowed per peer (32 defined here)
logs:
Steps to reproduce
network_params_das_local.yaml
configThe text was updated successfully, but these errors were encountered: