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

Look into allowing masternode upgrades without downtime #61

Open
tohsnoom opened this issue Jul 14, 2018 · 1 comment
Open

Look into allowing masternode upgrades without downtime #61

tohsnoom opened this issue Jul 14, 2018 · 1 comment

Comments

@tohsnoom
Copy link
Member

I believe when nothing in the masternode list information changes, masternodes can be upgraded without downtime when you swap the executable and only briefly bring it down to restart. However, when the protocol number changes, this may be causing each masternode's place in the list to be reset as the change is detected.

This request would be to investigate if this is indeed the case, and if so, if it would be safe and secure to allow masternodes to be upgraded to a new protocol version and allow a change to just that one attribute without resetting the masternode's place in the list.

@KolbyML
Copy link

KolbyML commented Jul 15, 2018

with dash i believe the masternode is only effect if down longer then a hour correct me if am wrong but that is what i heard. So yes i also believe that.

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

No branches or pull requests

2 participants