-
Notifications
You must be signed in to change notification settings - Fork 128
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
Mention v20 upgrades can take a few minutes #106
Comments
@wezrule What impacts to node operation are expected during this upgrade time? Is the node still expected to be participating on the network and responding to all RPC calls, etc.? |
The upgrade is synchronous and the node won't be participating or queryable during this. Even with the database upgrade for the epoch 2 preparation, the total downtime should be < 10 minutes |
Also mention that the ledger may grow in capacity by ~50%. A live ledger went from 16GB (before upgrade) to 24GB after. This is due to essentially copying all the state blocks to a new database while the old ones are still occupying space before being deleted. I experimented with using |
We can note this in the migration page: https://docs.nano.org/releases/node-releases/#v200 |
And done #156 |
nanocurrency/nano-node#2283 is modifying all accounts to use the representative account instead of the representative block. This has been found to take a few minutes on some systems.
The
account_info
RPC should markrep_block
as deprecated and the representative shown by default when it eventually gets removed, RPC 2.0?The text was updated successfully, but these errors were encountered: