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

fix: only processing streaming jobs that are in the 'created' state in auto-scaling #15000

Merged
merged 4 commits into from
Feb 5, 2024

Conversation

shanicky
Copy link
Contributor

@shanicky shanicky commented Feb 5, 2024

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

What's changed and what's your intention?

as title, related #14992 .

Checklist

  • I have written necessary rustdoc comments
  • I have added necessary unit tests and integration tests
  • All checks passed in ./risedev check (or alias, ./risedev c)

@@ -751,6 +754,7 @@ impl GlobalBarrierManagerContext {
guard
.table_fragments()
.iter()
.filter(|&(_, table)| matches!(table.state(), State::Created))
Copy link
Contributor Author

Choose a reason for hiding this comment

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

for auto scale in recovery (scale in & scale down)

Copy link
Contributor

Choose a reason for hiding this comment

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

In the future perhaps we will permit scaling for background ddl 🤔 . Perhaps we should add a comment for it.

Copy link
Member

Choose a reason for hiding this comment

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

Good catch, filtering by Running actors should work.

@@ -2528,6 +2528,7 @@ impl GlobalStreamManager {
guard
.table_fragments()
.iter()
.filter(|&(_, table)| matches!(table.state(), State::Created))
Copy link
Contributor Author

Choose a reason for hiding this comment

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

for auto scale in normal scenario (scale up & scale out)

Copy link
Member

@yezizp2012 yezizp2012 left a comment

Choose a reason for hiding this comment

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

LGTM, let's see if the issue still exist for background ddl recovery tests.

@github-actions github-actions bot added the type/fix Bug fix label Feb 5, 2024
@shanicky shanicky added this pull request to the merge queue Feb 5, 2024
Merged via the queue into main with commit c1a1286 Feb 5, 2024
40 checks passed
@shanicky shanicky deleted the peng/fix-scale-creating branch February 5, 2024 12:47
github-actions bot pushed a commit that referenced this pull request Feb 5, 2024
shanicky pushed a commit that referenced this pull request Feb 5, 2024
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.

3 participants