Prevent run.sh from running beyond the first epoch under normal use (#4498)

The local cluster that run.sh starts will typically only have a single
node, the bootstrap leader.  With epoch warmup enabled, run.sh will fail
after ~90 seconds once the warmup period has been exceeded due to lack
of votes from other validators.

As a workaround, disable epoch warmup and set slots-per-epoch to 1
million to keep run.sh alive for more than a fortnight.
This commit is contained in:
Michael Vines
2019-05-31 15:42:32 -07:00
committed by GitHub
parent 64e8a21d73
commit d343c409e6
2 changed files with 8 additions and 0 deletions

2
run.sh
View File

@ -72,6 +72,8 @@ solana-genesis \
--bootstrap-leader-lamports 10000000 \
--lamports-per-signature 1 \
--hashes-per-tick sleep \
--disable-epoch-warmup \
--slots-per-epoch 1000000 \
--mint "$dataDir"/config/drone-keypair.json \
--bootstrap-leader-keypair "$dataDir"/config/leader-keypair.json \
--bootstrap-vote-keypair "$dataDir"/config/leader-vote-account-keypair.json \