This repository has been archived by the owner on Jan 22, 2025. It is now read-only.
Preserve pre-existing vote/stake keypairs for bootstrap validator #19405
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CriesofCarrots
added
v1.7
automerge
AshwinSekar
added a commit
to AshwinSekar/solana
that referenced
this pull request
Nov 29, 2021
…ator (solana-labs#19405)" This reverts commit d559426.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
When rebooting a test cluster from a snapshot, the validators need to use the same vote accounts, and it is possible to provide these static keypairs via a
/keypairsdirectory. This works well for non-bootstrap validators, butremote-node.shcreates a new vote account for the bootstrap-validator on every run, causing that node's stake to be always delinquent.Summary of Changes
Add handling to look for bootstrap stake- and vote-account keypairs in
/keypairs