Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
archive: Implement archive_unstable_storage #1846
archive: Implement archive_unstable_storage #1846
Changes from 14 commits
7fe61dd
e8d3d8a
56e03db
316f116
c5886c0
077f2f5
cf050f7
e4de233
044941e
1cde37d
d560bb7
f29b761
5914660
038eb41
90f5e9b
f4f1b23
1de7eb2
dd70064
8ad9513
2be9f52
2134bf4
553f445
6f3920e
0580429
3cf59a8
899fa7a
688e3fb
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is
self.storage_max_queried_items
part of the spec? What is the value we use in production for this?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I can understand the spec, there's no explicit mention of an upper limit before the pagination kicks in. This is by design, since smoldot / other implementation might be running under hardware constraints.
For
chainHead_storage
we are using 5 items, but we haven't collect yet any data to make a better informed decision:polkadot-sdk/substrate/client/rpc-spec-v2/src/chain_head/chain_head.rs
Lines 85 to 87 in f4f1b23
The
archive
class is not exposed by substrate yet, but would keep both classes in syncThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be to good to add a prometheus metric for that or some annoying log for us to know whether this limit is exceeded often or not ^^
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not exactly sure about the semantics we want to have here. If the key is not queryable should it be counted as discarded item?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed this is a bit left to interpretation, I had to revisit the spec to get a better idea of it:
I'll add a small PR to clarify this behavior, both in chainHead and archive
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've removed the concept of non-querieable keys, as per comment: paritytech/json-rpc-interface-spec#118 (comment)