-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Snapshot restoration overhaul #11219
Changes from 19 commits
a2a3257
c543a46
86f0450
e250df2
5655285
9e79bc0
41f583c
ec6e4a5
74ce5e8
241675f
b8a1504
956e237
f7c7a8a
3ab9017
34cef68
fff43cc
f4ccf20
decb18c
d79a4f4
ebab778
2e75fb4
5970b80
100ca6b
bd9fc20
29a26c9
ac4cd10
81d46cb
d2c347a
1ebd119
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -676,7 +676,6 @@ impl<C> Service<C> where C: SnapshotClient + ChainInfo { | |
} else if manifest.state_hashes.contains(&hash) { | ||
true | ||
} else { | ||
warn!(target: "snapshot", "Hash of the content of {:?} not present in the manifest block/state hashes.", path); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. why removed? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Because it's not an abnormal condition, it's expected when we start syncing. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. To elaborate on that: when we see that there was a partial restoration going on before us, we try to re-use the chunks we already have on disk. This warning looks scary to users but it's not really something we need to worry about I think: it just means we can't use the chunk because we're now working on a different snapshot. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is that a yes? put the log back as a There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. either way is fine :) |
||
return Ok(false); | ||
}; | ||
|
||
|
@@ -788,6 +787,7 @@ impl<C> Service<C> where C: SnapshotClient + ChainInfo { | |
false => Ok(()) | ||
} | ||
} | ||
// todo[dvdplm] aren't we tossing away any errors from feed_state/feed_blocks here? And why the explicit `drop` here? | ||
dvdplm marked this conversation as resolved.
Show resolved
Hide resolved
|
||
other => other.map(drop), | ||
}; | ||
(res, db) | ||
|
Uh oh!
There was an error while loading. Please reload this page.