Strategy for enabling memtries during stateful-to 8000 -stateless validation protocol upgrade #11240
Assignees
Labels
A-stateless-validation
Area: stateless validation
Comments
|
Since @robin-near is involved in the initial discussions around this, assigning to Robin for now. |
|
we already have near/near-one-project-tracking#65 so we will want to clean one of them up |
|
Closing this as it's tracked in near/near-one-project-tracking#65 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Identify the right way to enable memtrie during the stateful-to-stateless validation protocol upgrade.
Before the upgrade all nodes will track all shards and they will start tracking only one or some shards after the upgrade. Memtrie is expected to be enabled in the case of tracking single or some shards, as it requires more memory. However, we may also need to think about how to make the transition from (stateful + disk tries) to (stateless + memtries). During this, we may need to run nodes with memtries while tracking all shards. Assuming this is the path to follow, we need to follow-ups.
Profile the memory usage needed to do that (a similar task opened for RPC nodes tracking all nodes:
Profile memory usage requirements of RPC and archival nodes in stateless validation #11230)
Make sure after the protocol upgrade the memtries for the shards that are not tracked in the new epoch are unloaded, leaving the nodes only with memtries for their tracked shards.
Related thread here.
The text was updated successfully, but these errors were encountered: