-
Notifications
You must be signed in to change notification settings - Fork 599
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: remove unexpected memory watermark update #19366
Conversation
@@ -531,11 +530,6 @@ impl LocalBarrierWorker { | |||
barrier: &Barrier, | |||
request: InjectBarrierRequest, | |||
) -> StreamResult<()> { | |||
if barrier.kind == BarrierKind::Initial { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems this is the only usage of watermark_epoch
of actor_manager
. If we don't use it anymore, we can remove it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's also used to propagate the watermark to executors.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Should we cherry pick to 2.1? |
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Since watermark sequence is utilized for operator memory management, this ticker should be the sole location for setting the watermark.
This PR removes the additional watermark setting during
BarrierKind::Initial
. This operation introduces uncertainty, i.e.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.