Open staffik opened 6 days ago
Attention: Patch coverage is 37.25490%
with 32 lines
in your changes missing coverage. Please review.
Project coverage is 71.79%. Comparing base (
59e2b88
) to head (489ed1d
). Report is 1 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Can you test that it works well when the shard assignment is changing and the node should state sync?
Tested in forknet20, I will add a dedicated pytest.
Part of: https://github.com/near/near-one-project-tracking/issues/65 An option for non-validator node to track shards of given validator.
During stateful -> stateless protocol upgrade a node will track all shards and will require a lot of RAM. After the migration we can move the validator key to a new, smaller node, that does not track all shards. To make it with minimal downtime, the new node needs to have appropriate shards in place and memtries loaded in memory, then we hot swap the validator key without stopping the new node. But before that happen the new node is not a validator and we need a way to tell it which validator's shards it should track.