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
Is your feature request related to a problem? Please describe.
No.
I am tired so will try to explain what I am thinking.
I am thinking redundancy for node runners to be able to have a reliable service in case of hardware fail's, sd card gets corrupt etc
would it be possible to have a feature request to develop nodes for failover in a master -> slave or master -> slave -> slave configuration?
This would provide some form of redundancy for node runners and can only help Mysterium as a whole.
The idea would be each node sends a heart beat to the other active node and if it stops then a slave node will take over, this would limit downtime of an endpoint to literally seconds or ms and keep up the reliability of the end nodes and service as a whole.
I have posted this in the wizards channel on discord but things get lost in the chat when many posts are made.
Describe the solution you'd like
Redundancy of end nodes.
Describe alternatives you've considered
Currently I run a proxmox cluster with HA so if my node goes down it spins up another on a different server but I am thinking of node runners in general and how to maximise there quality and uptime of there nodes and keep the myst rolling in for them and reliability for Mysterium as a whole.
I believe thinking about redundancy is the right direction to take as a service provider to limit complaints of nodes going down etc.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
No.
I am tired so will try to explain what I am thinking.
I am thinking redundancy for node runners to be able to have a reliable service in case of hardware fail's, sd card gets corrupt etc
would it be possible to have a feature request to develop nodes for failover in a master -> slave or master -> slave -> slave configuration?
This would provide some form of redundancy for node runners and can only help Mysterium as a whole.
The idea would be each node sends a heart beat to the other active node and if it stops then a slave node will take over, this would limit downtime of an endpoint to literally seconds or ms and keep up the reliability of the end nodes and service as a whole.
I have posted this in the wizards channel on discord but things get lost in the chat when many posts are made.
Describe the solution you'd like
Redundancy of end nodes.
Describe alternatives you've considered
Currently I run a proxmox cluster with HA so if my node goes down it spins up another on a different server but I am thinking of node runners in general and how to maximise there quality and uptime of there nodes and keep the myst rolling in for them and reliability for Mysterium as a whole.
I believe thinking about redundancy is the right direction to take as a service provider to limit complaints of nodes going down etc.
The text was updated successfully, but these errors were encountered: