feat(snapshot-backfill): measure accumulated row count for each vnode stream #20016
+236
−29
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.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Part of #19720
Measure the row count of each vnode stream, so that the row count can be saved in the state to be introduced in #19720.
This PR will also fix a bug found in the CI #19720. In short, the bug is caused by the use of
FuturesUnordered
. InFuturesUnordered
, pending futures will be stored separately and will not be polled until a special cx generated inFuturesUnordered::poll_next
is awakened. However, when we usePeekable::peek
to peek the latest progress of the stream, the special cx will be overwritten when we poll thePeek
future, and then even the future is ready after peeked, it is still not in the ready queue, and will not be polled and get stuck forever.Tests are added to cover the bug.
Checklist
Documentation
Release note