refactor: maintain subscriptions in local barrier worker #18516
Merged
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?
Previously when build actor and inject barrier are not done together, we have to include the barrier information together with the
StreamActor
to a combinedBuildActorInfo
when we build the actor. After we change to build actor when inject barrier in #18270, we are able to get the subscription information from local barrier worker.Therefore, in this PR, we won't generate the actor subscription info on meta node to generate the
BuildActorInfo
, but instead include only theStreamActor
in theInjectBarrierRequest
. Meanwhile, we incrementally maintain the global subscription info in the local barrier worker so that we can pass the subscription info when we build actors.Checklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.