Beacon node not honoring p2p-max-peers value
mcdee opened this issue · comments
Describe the bug
Starting prysm with --p2p-max-peers=64 I'm seeing larger numbers of peers on many nodes, e.g.
curl -s http://localhost:8080/metrics | egrep '^connected_libp2p_peers{'
connected_libp2p_peers{agent="lighthouse"} 26
connected_libp2p_peers{agent="lodestar"} 5
connected_libp2p_peers{agent="nimbus"} 13
connected_libp2p_peers{agent="prysm"} 27
connected_libp2p_peers{agent="rust-libp2p"} 1
connected_libp2p_peers{agent="teku"} 15
connected_libp2p_peers{agent="unknown"} 1
Has this worked before in a previous version?
No response
🔬 Minimal Reproduction
No response
Error
No response
Platform(s)
No response
What version of Prysm are you running? (Which release)
beacon-chain version Prysm/v5.0.3/38f208d70dc95b12c08403f5c72009aaa10dfe2f. Built at: 2024-04-04 18:32:19+00:00
Anything else relevant (validator index / public key)?
No response