Skip to content
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(meta): only store CreateStreamingJob command in tracker #17742

Merged
merged 5 commits into from
Jul 19, 2024

Conversation

wenym1
Copy link
Contributor

@wenym1 wenym1 commented Jul 18, 2024

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

After #17428, the command finish notifier is removed, and for command other than CreateStreamingJob, we simply store it the in CreateMviewTracker and don't do anything on it. Therefore, in this PR, we change to only store the CreateStreamingJob command in the tracker.

The following refactors are done accordingly or by the way:

  • Extra the fields in the original CreateStreamingJob to a separate struct CreateStreamingJobCommandInfo
  • Change to wrap the tracker with a parking-lot mutex rather than a async mutex.

Checklist

  • I have written necessary rustdoc comments
  • I have added necessary unit tests and integration tests
  • I have added test labels as necessary. See details.
  • I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
  • My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
  • All checks passed in ./risedev check (or alias, ./risedev c)
  • My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)
  • My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

  • My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

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.

@wenym1 wenym1 requested review from hzxa21, yezizp2012 and kwannoel July 18, 2024 09:21
@kwannoel
Copy link
Contributor

Looks like recovery test is failing. Will take a look after it pass.

@wenym1
Copy link
Contributor Author

wenym1 commented Jul 19, 2024

Looks like recovery test is failing. Will take a look after it pass.

The test has passed. It's caused by a bug described in #17613 (comment).

@kwannoel PTAL

@@ -22,13 +22,16 @@ use crate::barrier::Command;
use crate::manager::{ActiveStreamingWorkerNodes, ActorInfos, InflightFragmentInfo, WorkerId};
use crate::model::{ActorId, FragmentId};

#[derive(Debug, Clone)]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add some docs for this? Is it for any new fragments associated with the barrier command?

And what is the is_injectable field for, when is it true/false?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is_injectable means whether we need to inject the barrier directly to the actors of the fragment. The struct is just extracted from the CommandFragmentChanges::NewFragment, and no logic is changed in this PR.

These fragments are the most upstream fragments, such as source, now.

},
&version_stats,
) {
if let Some(command) = tracker.add(&command_ctx, &version_stats) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here

@kwannoel
Copy link
Contributor

Rest LGTM.

@wenym1 wenym1 added this pull request to the merge queue Jul 19, 2024
Merged via the queue into main with commit 9335967 Jul 19, 2024
30 of 31 checks passed
@wenym1 wenym1 deleted the yiming/refactor-create-mv-tracker branch July 19, 2024 09:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants