fix(file source): clear counter splits_on_fetch
when updating rate limit
#20622
+2
−4
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?
Close #20593
How to reproduce
upload file1
ALTER SOURCE s1 SET source_rate_limit TO 0;
upload file2
ALTER SOURCE s1 SET source_rate_limit TO default;
upload file 3 4 5
File 3 4 5 cannot be read, but is in the fetch state table.
root cause
This is a bug that only occurs when applying rate limits on the file source. After updating the rate limit, we set
need_rebuild_reader
to true, but we do not sync the modification ofsplits_on_fetch
. Each time we callreplace_with_new_batch_reader
, it reads the state table of the fetch executor and updates the counter forsplits_on_fetch
. As a result, this leads to pending files being counted twice during this period. Subsequently, becausesplits_on_fetch
is not zero, it causes further files to remain pending.Checklist
Documentation
Release note