Skip to content
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

Redundancy for node runners. #5910

Open
liamgibbins opened this issue Nov 5, 2023 · 0 comments
Open

Redundancy for node runners. #5910

liamgibbins opened this issue Nov 5, 2023 · 0 comments

Comments

@liamgibbins
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant