MainNet and TestNet Upgrade: v2.1.3

Hi All,

Algorand v2.1.3 MainNet and TestNet availability is planned for August 19th at approximately 10:30am ET. Release notes are available here: https://github.com/algorand/go-algorand/releases/tag/v2.1.3-stable and documentation has been updated at https://developer.algorand.org/. This upgrade is a consensus upgrade so there will be 10k block voting period(s) followed by a 140k block (or approximately 7 days) waiting period once accepted before the consensus upgrade occurs.

5 Likes

Update on timing: We expect the upgrade to v2.1.3 to be publicly available at approximately 12:00pm ET today (Noon 8/19/2020).

The upgrade to v2.1.3 is now publicly available.

2 Likes

I have done the “mainnet update” using

./update.sh -i -c stable -p ~/node -d ~/node/data -n

Now
./goal node start -d data

is cosuming CPU, but the prompt is not returned.
What do you suggest?

(By the way, betanet and testnet update is OK).

$ tail node.log
{“file”:“acctupdates.go”,“function”:“github.com/algorand/go-algorand/ledger.(*accountUpdates).accountsInitialize”,“level”:“info”,“line”:934,“msg”:“accountsInitialize still building the trie, and processed so far 3604480 accounts”,“name”:"",“time”:“2020-08-19T18:28:49.534301+02:00”}
{“file”:“acctupdates.go”,“function”:“github.com/algorand/go-algorand/ledger.(*accountUpdates).accountsInitialize”,“level”:“info”,“line”:934,“msg”:“accountsInitialize still building the trie, and processed so far 3670016 accounts”,“name”:"",“time”:“2020-08-19T18:28:59.264386+02:00”}
{“file”:“acctupdates.go”,“function”:“github.com/algorand/go-algorand/ledger.(*accountUpdates).accountsInitialize”,“level”:“info”,“line”:934,“msg”:“accountsInitialize still building the trie, and processed so far 3735552 accounts”,“name”:"",“time”:“2020-08-19T18:29:09.037118+02:00”}
{“file”:“acctupdates.go”,“function”:“github.com/algorand/go-algorand/ledger.(*accountUpdates).accountsInitialize”,“level”:“info”,“line”:934,“msg”:“accountsInitialize still building the trie, and processed so far 3801088 accounts”,“name”:"",“time”:“2020-08-19T18:29:19.941051+02:00”}

{“file”:“acctupdates.go”,“function”:“github.com/algorand/go-algorand/ledger.(*accountUpdates).accountsInitialize”,“level”:“info”,“line”:952,“msg”:“accountsInitialize rebuilt the merkle trie with 4276913 entries in 6m37.898899817s”,“name”:"",“time”:“2020-08-19T18:30:49.055709+02:00”}
{“callee”:“github.com/algorand/go-algorand/ledger.(*accountUpdates).initializeFromDisk.func1”,“caller”:"/root/go/src/github.com/algorand/go-algorand/ledger/acctupdates.go:716",“file”:“dbutil.go”,“function”:“github.com/algorand/go-algorand/util/db.(*Accessor).atomic”,“level”:“warning”,“line”:355,“msg”:“dbatomic: tx surpassed expected deadline by 7m34.356102826s”,“name”:"",“readonly”:false,“time”:“2020-08-19T18:30:55.756733+02:00”}
{“file”:“acctupdates.go”,“function”:“github.com/algorand/go-algorand/ledger.(*accountUpdates).vacuumDatabase.func1”,“level”:“info”,“line”:1741,“msg”:“Vacuuming accounts database started”,“name”:"",“time”:“2020-08-19T18:30:55.860796+02:00”}
{“file”:“acctupdates.go”,“function”:“github.com/algorand/go-algorand/ledger.(*accountUpdates).vacuumDatabase.func1”,“level”:“info”,“line”:1745,“msg”:“Vacuuming accounts database in progress”,“name”:"",“time”:“2020-08-19T18:31:00.861592+02:00”}

{“Context”:“Agreement”,“Hash”:“56LTB2YGVM5OK7SEWOVMSV5DVWCMUDHUKXGXTDWM6K5LBQTDACIQ”,“ObjectPeriod”:0,“ObjectRound”:8557792,“ObjectStep”:2,“Period”:0,“Round”:8557792,“Sender”:“42GALMKS3HMDB24ZPOR237WQ5QDHL5NIRC3KIA4PCKENJZAD5RP5QPBFO4”,“Step”:2,“Type”:“VoteAccepted”,“Weight”:42,“WeightTotal”:944,“file”:“trace.go”,“function”:“github.com/algorand/go-algorand/agreement.(*tracer).logVoteTrackerResult”,“level”:“info”,“line”:477,“msg”:“vote accepted for {{} 0 3V2MC7WJGAFU2EHWBHEETIMJVFJNAT4KKWVPOMJFJIM6ZPWEJRJ4POTXGI 56LTB2YGVM5OK7SEWOVMSV5DVWCMUDHUKXGXTDWM6K5LBQTDACIQ 67WIHACYMQYZA7U72MFBUHYWS4GGPJXTAB2T7ZX2WXMOSROKLCUA} at (8557792, 0, 2)”,“time”:“2020-08-19T18:34:53.650497+02:00”}
{“Context”:“Agreement”,“Hash”:“56LTB2YGVM5OK7SEWOVMSV5DVWCMUDHUKXGXTDWM6K5LBQTDACIQ”,“ObjectPeriod”:0,“ObjectRound”:8557792,“ObjectStep”:2,“Period”:0,“Round”:8557792,“Sender”:“EOZWAIPQEI23ATBWQ5J57FUMRMXADS764XLMBTSOLVKPMK5MK5DBIS3PCY”,“Step”:2,“Type”:“VoteAccepted”,“Weight”:41,“WeightTotal”:985,“file”:“trace.go”,“function”:“github.com/algorand/go-algorand/agreement.(*tracer).logVoteTrackerResult”,“level”:“info”,“line”:477,“msg”:“vote accepted for {{} 0 3V2MC7WJGAFU2EHWBHEETIMJVFJNAT4KKWVPOMJFJIM6ZPWEJRJ4POTXGI 56LTB2YGVM5OK7SEWOVMSV5DVWCMUDHUKXGXTDWM6K5LBQTDACIQ 67WIHACYMQYZA7U72MFBUHYWS4GGPJXTAB2T7ZX2WXMOSROKLCUA} at (8557792, 0, 2)”,“time”:“2020-08-19T18:34:53.651017+02:00”}

OK, node finally started.
It took nearly 10 minutes!

There is a one time accounts db migration that will take a few minutes. It should start up normally once this is complete.

1 Like

I think you’re running an archival node, am I correct ?

The upgrade process can take a longer time, but it’s going to be a one time thing, as John mentioned.

The timing are greatly depends on the CPU, memory and disk configuration.

What block is the consensus proposal going out in?

There are two windows in the upgrade process - there is repeating (if necessary) voting window for approval. Once that is complete there is a 140k block waiting period until the network all moves to the new consensus version on the same block. This voting period ends on block 8,564,687. If it the voting period is successful, the upgrade will be 140k blocks later. If not, a new 10k round voting period will begin.

1 Like

At least on mainnet, nothing has been pushed out yet.
What pushes that out and where can I find specifics on the consensus protocol upgrade process?

Last committed block: 8562524
Time since last block: 1.4s
Sync Time: 0.0s
Last consensus protocol: https://github.com/algorandfoundation/specs/tree/e5f565421d720c6f75cdd186f7098495caf9101f
Next consensus protocol: https://github.com/algorandfoundation/specs/tree/e5f565421d720c6f75cdd186f7098495caf9101f
Round for next consensus protocol: 8562525
Next consensus protocol supported: true

Here is a description of the upgrade process: https://algorand.foundation/protocol-development

The new binaries are available on GitHub and well as in the appropriate repos for auto updates if you have them configured.

1 Like