-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chain Node failover not working #200
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If I have 2 Lotus Full Chain Nodes and add both to Curio, there are a few issues:
My base config contains the api info for two Chain Nodes.
If I stop the Chain Node that curio is using, curio just shows the failed chain connectivity and never kicks over to using the other Chain Node.
I have tested both Chain Nodes from 2 different boosts, and both are accessible. Also using one at a time in Curio, they are both accessible.
I tried to restart the node without the 10.4.10.201 Full Chain Node and it fails with this:
Then, I restarted that 10.4.10.201 Full Chain Node and restarted curio node.
Still only 10.4.10.201 showed in the Chain Connectivity.
Then I hit the little "Move Up" arrow in the base layer config to move 10.4.9.201 to Item 1.
Now it shows 2 Chain Nodes:
Interesting.
If I move 10.4.10.201 into "Item 1", then curio only shows one Chain Connectivity.
If I move 10.4.9.201 into "Item 1", then curio shows both Chain Nodes.
And even when both Chain Nodes shows in Chain connectivity, as soon as I stop the Chain node that is actively being used, Curio does not switch over to the other Chain Node. (even after 10 minutes).
If I then stop and start the curio node, it fails to start with the Chain Node that was last active:
The text was updated successfully, but these errors were encountered: