You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(core+tool): epochs_v2 backfill and formal-restore cleanup (#11870)
# Description of change
Some cleanup for #11697
- **Local epoch backfill: only missing data counts as pruned
(`iota-core`, `iota-types`).** Real storage failures were swallowed as
"data pruned, retry once a newer snapshot is published". Absent-data
errors now carry `Kind::Missing` (was `custom`) and only those end the
best-effort replay; anything else propagates. Nothing else reads the
kind.
- **Operator doc fixes (`iota-config`, `docs`).** The config doc still
described the removed background task (the backfill is synchronous and
gates startup); the snapshots guide now documents the refuse-to-start
case when even the latest snapshot is older than the node's pruned-away
history.
## How the change has been tested
- [x] Basic tests (linting, compilation, formatting, unit/integration
tests)
- [ ] Patch-specific tests (correctness, functionality coverage)
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] I have checked that new and existing unit tests pass locally with
my changes
Copy file name to clipboardExpand all lines: docs/content/operator/common/snapshots.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -249,7 +249,7 @@ state-snapshot-read-config:
249
249
250
250
</Tabs>
251
251
252
-
With this set, the node downloads the per-epoch metadata from the latest formal snapshot at startup (a few seconds; the large object files are not downloaded) and then starts normally.
252
+
With this set, the node downloads the per-epoch metadata from the latest formal snapshot at startup (a few seconds; the large object files are not downloaded) and then starts normally. If even the latest snapshot is older than the node's executed history and the missing epochs' data is already pruned locally, the node still refuses to start: wait for a newer snapshot, restore from a formal snapshot, or disable the gRPC API.
0 commit comments