refactor(stream): do not broadcast actor info in shared context #21258
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.
Highest Release Version: 2.3
What's changed and what's your intention?
Previously we broadcast the
ActorInfo
of globally all running actors to theSharedContext
of each CN, so that theDispatchExecutor
andMergeExecutor
can get the host of downstream or upstream actors to establish the exchange connection.In #21256, we already unified remote and local output so that the
DispatchExecutor
won't need theActorInfo
of downstream actor. In this PR, instead of only providing with upstream actor_ids, we will change to provide the upstreamActorInfo
directly forMergeExecutor
, either in build actor info, orMergeUpdate
, so thatMergeExecutor
also won't need to getActorInfo
fromSharedContext
, and in the end, we don't have to broadcast and maintain the global list ofActorInfo
anymore.Checklist
Documentation
Release note