refactor: move source retry inside reader stream #20526
Open
+275
−205
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?
replacement of #20295
the intuition is to handle the crash loop when upstream is unavailable and now we only report error when the exec is first executed.
Source backfill does not need to change because when it is doing backfilling, a recover will lead to cancel the job, instead of rebuilding the actor. So when upstream is unavailable, it does not panic RisingWave in recovery.
Checklist
Documentation
Release note