Skip to content

1.38.0
Compare
Choose a tag to compare
@marcelo-gonzalez marcelo-gonzalez released this 18 Mar 18:58
· 1292 commits to master since this release
1.38.0
aac5e42 
CODE_COLOR: CODE_YELLOW_MAINNET
RELEASE_VERSION: 1.38.0
PROTOCOL_UPGRADE: TRUE
DATABASE_UPGRADE: FALSE
SECURITY_UPGRADE: FALSE

Protocol Upgrade Voting

This release contains a protocol upgrade. Voting for upgrading to protocol version 65 will start on Wednesday 2024-03-20 14:00:00 UTC. Depending on epoch durations, resharding is expected to happen around Wednesday 2024-03-20 18:00 UTC +/-4h, and protocol adoption is expected to happen around Thursday 2024-03-21 10:00 UTC +/-4h. Resharding and adoption times are only estimates, since many factors influence them.

Managing Resharding

This protocol upgrade includes resharding of shard 2. Which means that after protocol upgrade we will have 6 shards. New shard split is defined by these border accounts vec!["aurora", "aurora-0", "game.hot.tg", "kkuuue2akv_1630967379.near", "tge-lockup.sweat"]

Important points:

  • Resharding will happen in the epoch RIGHT AFTER protocol voting epoch (and RIGHT BEFORE actual protocol upgrade).
  • If your node fails to reshard before protocol upgrade, it will not be able to continue being a part of the chain. If that happens, you should restart from a Pagoda provided backup.
  • Resharding creates a database snapshot that is deleted right after resharding is finished. This snapshot will not take extra space at first, but you may notice a progressive increase of data folder size up to around 50GB higher than before. There should no longer be an issue with the data directory increasing to an unmanageable size.
  • To monitor resharding you can use metrics near_resharding_status, near_resharding_batch_size, and near_resharding_batch_prepare_time_bucket. You can read more here https://github.com/near/nearcore/blob/master/docs/architecture/how/resharding.md#monitoring.
  • If you observe problems with block production or resharding performance, you can adjust resharding throttling configuration. Read more here https://github.com/near/nearcore/blob/master/docs/architecture/how/resharding.md#monitoring.
  • RAM usage during resharding is around 8-10GB.

Full resharding doc can be found here https://github.com/near/nearcore/blob/master/docs/architecture/how/resharding.md.

Protocol Changes

  • Resharding v3 - resharding of shard 2 implemented by #10725

Known issues

  • This release removes state snapshot compaction configuration options, as they are no longer needed. Your node may emit a warning that those configuration options are not recognized, but this is not an issue.
Assets 2
Loading