oasisprotocol / oasisprotocol/oasis-core
Backfill historic runtime state after restoring from a checkpoint
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Currently runtime storage nodes automatically restore from checkpoints when possible. This may cause the storage nodes to contain gaps in their historic state. One possibility would be for storage nodes to also backfill historic state after a checkpoint restore (as a background job with lower priority perhaps).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the runtime storage-node checkpoint restore path and how historic state is represented and queried. Determine how a background, lower-priority backfill could recover state missing after restore, then verify that restored nodes no longer contain historic gaps without disrupting normal runtime work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100