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
On startup of a node, the node will spam GetPeers requests to each peer until the node receives a peer list packet from the peer. The issue is that the peer seems to respond with the peer list as many times as the node requested it. I've seen this result in as many as 40 duplicate peer lists being sent back to the node.
Attached at the bottom of this is a packet dump that demonstrates what it is happening.
Take note of the packets with payload of 00000011e4dfbbb9aeaff2c844181d5f031f2cac00 and their timestamps. This is the node requesting a peer list from the peer.
Also take note of the 'count': 14, packet. This packet is violating the networking protocol and seems to have multiple duplicate payloads stuffed into it. This is may be a separate issue altogether, but it does seem related.
I'm pretty sure the issue here is that on startup, zeno will ask the seed for peers, and it return peers, and then it will ask each of those nodes for peers, and they will return peers, and it will keep creating this expontential peer query explosion until those peers connect back. They should connect back very quickly, but it can still generate alot of messages.
On startup of a node, the node will spam GetPeers requests to each peer until the node receives a peer list packet from the peer. The issue is that the peer seems to respond with the peer list as many times as the node requested it. I've seen this result in as many as 40 duplicate peer lists being sent back to the node.
Attached at the bottom of this is a packet dump that demonstrates what it is happening.
Take note of the packets with payload of
00000011e4dfbbb9aeaff2c844181d5f031f2cac00
and their timestamps. This is the node requesting a peer list from the peer.Also take note of the
'count': 14,
packet. This packet is violating the networking protocol and seems to have multiple duplicate payloads stuffed into it. This is may be a separate issue altogether, but it does seem related.The text was updated successfully, but these errors were encountered: