There is a set of issues that we are aware of, some have fixes others that need to be implemented.
We need a good workaround to reduce these incidents as it sometimes results in a node having very few peers (as little as one) and sometimes totally loosing all connectivity with joystream nodes. This is resulting in network splits.
Over last few days we noticed some nodes logging very frequent messages like:
Banning PeerId("QmS8Gi18TmDwLv7Yr5TYmH9vQc2ydRZ8nx7a79pemfguUF") because "Peer is on different chain (our genesis: 0x78be…87c7 theirs: 0xcd89…97b2)"and
Received extra substream after having already one open in backwards-compatibility mode with PeerIdThis is a result of the network discovering other peers running different networks because of the shared DHT. see https://github.com/libp2p/rust-libp2p/issues/1087
There is a set of issues that we are aware of, some have fixes others that need to be implemented.
We need a good workaround to reduce these incidents as it sometimes results in a node having very few peers (as little as one) and sometimes totally loosing all connectivity with joystream nodes. This is resulting in network splits.
Current workaround is to increase
--in-peersand--out-peersto make enough slots available. We should be able to import this fix: https://github.com/paritytech/substrate/commit/8bc576f5c10e189bc4bf77335b40f60d46b94949