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.

Sign up for GitHub

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

Jump to bottom

Parquet Source: Alter source_rate_limit=0 sometimes does not resume after altering back to default #20593

Closed
kwannoel opened this issue Feb 25, 2025 · 0 comments · Fixed by #20622
Closed

Parquet Source: Alter source_rate_limit=0 sometimes does not resume after altering back to default #20593

kwannoel opened this issue Feb 25, 2025 · 0 comments · Fixed by #20622
Assignees
@wcy-fdu
Labels
type/bug Something isn't working
Milestone
release-2.3

Comments

@kwannoel
Copy link
Contributor

kwannoel commented Feb 25, 2025 •
edited
Loading

Describe the bug

When altering parquet source rate limit to 0, and changing it back to default, the parquet source does not resume ingesting sometimes. And the compute node has to be restarted to make it resume.

Error message/log

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wcy-fdu wcy-fdu

Labels
type/bug Something isn't working
Projects
None yet
Milestone
release-2.3
Development

Successfully merging a pull request may close this issue.

fix(file source): clear counter splits_on_fetch when updating rate limit risingwavelabs/risingwave
2 participants
@kwannoel @wcy-fdu