Reconstruct data columns without blocking processing and import #5986
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.
Issue Addressed
Part of #4983. This is a work in progress.
The current sequence of reconstruction:
Proposed Changes
RuntimeVariableList
conversion for data columnsTODOs
I've also moved reconstruction after processing availability as my original intention was to not block import if the node already has enough custody columns. However, given we're assuming only supernodes perform reconstruction, this change may be not make much differences right now, although I think the API is a bit cleaner with the reconstruction logic separated from processing logic. Happy to hear other thoughts on this.
Additional Info
Below are logs from local testing, notice that the reconstruction blocks processing of incoming data columns (due to holding the availability cache write lock), and they gets ignored as duplicates: