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
Summary
with NEO2.x network, all consensus nodes communicate with each other with seed nodes, in the worst case, all seed nodes crash, this would happen in a very low possibility, then all seed nodes loss connection with consensus nodes, when they are brought back online again, they can not reconnect to the consensus nodes, because consensus nodes can't build a new connection with the seed nodes.
To rebuild the connection, it will requires all consensus nodes to restart.
Reproduction steps:
prepare 4 consensus nodes.
prepare 2 seed nodes.
start seed nodes
start 4 consensus nodes.
start two normal neo-cli clients.
shut down all seed nodes.
start seed nodes again.
Do you have any solution you want to propose?
We should add a policy to auto reconnect to the seed nodes when they are all down and back again, and then there is no need to restart all consensus nodes.
Where in the software does this update applies to?
Network Policy
P2P (TCP)
The text was updated successfully, but these errors were encountered:
How about this solution:
A node can maintain a connected peers file. When restart again, it can try to connect seed nodes, and also the peers in the file.
Then when seed nodes restart, they can join the network.
Summary
with NEO2.x network, all consensus nodes communicate with each other with seed nodes, in the worst case, all seed nodes crash, this would happen in a very low possibility, then all seed nodes loss connection with consensus nodes, when they are brought back online again, they can not reconnect to the consensus nodes, because consensus nodes can't build a new connection with the seed nodes.
To rebuild the connection, it will requires all consensus nodes to restart.
Reproduction steps:
Do you have any solution you want to propose?
We should add a policy to auto reconnect to the seed nodes when they are all down and back again, and then there is no need to restart all consensus nodes.
Where in the software does this update applies to?
The text was updated successfully, but these errors were encountered: