Closed m-e-m-f-i-s-19 closed 9 months ago
hi @m-e-m-f-i-s-19, this's not expected, we are checking it and will give feedback soon
+1
Hi @m-e-m-f-i-s-19 @zekchan We have noticed that one of the nodes is indeed behaving abnormally. Our current expectation is to have two peers operational. Previously, due to certain reasons, one of the bootnodes was unable to provide its services, but it has now been restored. Therefore, you should now be able to connect to two peers. However, this is not our intended final state. Due to some issues with the internal mechanisms of the bootnode, we are in the process of updating its node discovery logic. We expect to roll out this optimization soon, which will improve its ability to discover more p2p nodes. (As a result, the ENR address of our bootnode will also be updated) We apologize for any inconvenience this may have caused and are working diligently to complete these updates...
@m-e-m-f-i-s-19 @zekchan we've updated our geth bootnode version, including several static peers deployed in different regions. You can get at least 9 peers connected as expected, pls try it again. Sorry for the inconvenience...
@krish-nr thank you. so far everything works great 🚀
Node info:
op-geth: v0.2.1
op-node: v0.2.2
Start components
op-geth:
op-node:
Problem:
Always 1 peer connected.
Question:
Is this expected behavior? If not could the team explain how to fix that?