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
A node (node X) is considered offline by its peers even though he is running.
It happens because all other nodes are connected to it with "stale" connections.
In brief, when a node connect to node X, the connection is working and everything is good. But within 5 minutes, node X will trigger a "networking update". On node X (this is the first time we experience this), the "networking update" will leave the connections open but make them all stale (will not receive anything, and will send into the void). Everything will timeout.
On the screenshots we can see that connection is working until the "networking update" :
2 proposed solutions:
"networking update" also kills the connections
kill connection on timeout
The text was updated successfully, but these errors were encountered:
A node (node X) is considered offline by its peers even though he is running.
It happens because all other nodes are connected to it with "stale" connections.
In brief, when a node connect to node X, the connection is working and everything is good. But within 5 minutes, node X will trigger a "networking update". On node X (this is the first time we experience this), the "networking update" will leave the connections open but make them all stale (will not receive anything, and will send into the void). Everything will timeout.
On the screenshots we can see that connection is working until the "networking update" :
2 proposed solutions:
The text was updated successfully, but these errors were encountered: