docs/node/run-your-node/advanced: Add new pruning section #1526
Conversation
✅ Deploy Preview for oasisprotocol-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| To configure pruning it is recommended to set `n=250_000`. The maximum value is | ||
| `n=400_000`. If you need to preserve more data (e.g. nodes serving historical | ||
| state) you will have to keep the entire state from the genesis. |
There was a problem hiding this comment.
Unfortunately if you preserve runtime state, to serve historical queries, you are also forced to preserve all the consensus data, as consensus light block are computed ad-hoc (see). A requirement that should probably be documented somewhere.
We could open an issue, so that consensus light blocks are not computed ad-hoc and are instead stored in the separate DB, with different pruning config. This would allow to run Observer node with much lower hardware requirements, assuming most of the consensus data could be dropped.
Not sure this is a critical priority right now, but issue definitely cannot hurt...: oasisprotocol/oasis-core#6430
martintomazic
force-pushed
the
martin/task/update-pruning-documentation
branch
from
af27d24 to
f4fe4e5
Compare
martintomazic
force-pushed
the
martin/task/update-pruning-documentation
branch
from
f4fe4e5 to
dc2e4fb
Compare
|
We should probably wait with merging this until https://github.com/oasisprotocol/internal-ops/issues/1221 (snapshots without holes) is |
martintomazic
force-pushed
the
martin/task/update-pruning-documentation
branch
from
dc2e4fb to
9a3d510
Compare
martintomazic
force-pushed
the
martin/task/update-pruning-documentation
branch
from
9a3d510 to
79708d0
Compare
matevz
left a comment
matevz
left a comment
There was a problem hiding this comment.
I left some suggestions.
Can you also update https://github.com/oasisprotocol/docs/blob/martin/task/update-pruning-documentation/docs/node/run-your-node/prerequisites/hardware-recommendations.md?plain=1#L153-L168
Perhaps just title it "Pruning" and replace the links with the new one to your chapter.
|
|
||
| To configure pruning it is recommended to set `n=250_000`. The maximum value is | ||
| `n=400_000`. If you need to preserve more data (e.g. nodes serving historical | ||
| state) you will have to keep the entire state from the genesis. |
There was a problem hiding this comment.
you will have to keep the entire state from the genesis
Is this that speceific ParaTime's genesis or consensus? Where does the 400_000 limit come from?
There was a problem hiding this comment.
Yes Paratime specific, updated the text to make it clear.
Where does the 400_000 limit come from
Is not hard limit, but something that as from my experiments am willing to vouch it will still prune with reasonable speed.
martintomazic
force-pushed
the
martin/task/update-pruning-documentation
branch
from
79708d0 to
3f60752
Compare
Added new links, further refinement should be done as part of #1506 as is completely outdated :(. |
martintomazic
force-pushed
the
martin/task/update-pruning-documentation
branch
from
3f60752 to
2dbbd19
Compare
|
As agreed with the reviewer in private this was ready to be merged. Future refinements can be done in the follow up. |
Closes #1469.
Considerations
Possible follow-up
#1506
Hardening data availability.