-
Notifications
You must be signed in to change notification settings - Fork 147
Open
Description
Context
It has become impractical to keep all state from the genesis thus more and more nodes are pruning it.
Problem
- Pruning is already causing availability issues:
- E.g. https://github.com/oasisprotocol/internal-ops/issues/1281.
- Previous issues with emty validator set because of the missing light blocks.
- Consensus light blocks are computed ad-hoc, from the full state:
- Running observer with historical state requires all consensus data, just to fetch light blocks - see.
Solution:
- Create additional DB for consensus light blocks and query them from there.
- Independent full-state (NodeDB && blockstore) vs light state pruning.
- E.g. keep 1 year of light history by default (should be few
GBmax).
- E.g. keep 1 year of light history by default (should be few
Follow-ups:
- Similar thing should be done for the runtime state and its pruning (go: Storage committee worker should be responsible for both runtime light history and state #6400).
- History expiry.
Metadata
Metadata
Assignees
Labels
No labels