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

The file cache rate limit filter over-filters insertion than expected. #14156

Closed
MrCroxx opened this issue Dec 22, 2023 · 5 comments
Closed

The file cache rate limit filter over-filters insertion than expected. #14156

MrCroxx opened this issue Dec 22, 2023 · 5 comments
Assignees
Labels
no-issue-activity type/bug Something isn't working
Milestone

Comments

@MrCroxx
Copy link
Contributor

MrCroxx commented Dec 22, 2023

Describe the bug

The insert rate limit is set to 480MB/s (based on flush rate) and no more admission policy is enabled. But there are writers dropped even the flush throughput only reaches 400MB/s.

image

Error message/log

No response

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

@MrCroxx MrCroxx added the type/bug Something isn't working label Dec 22, 2023
@MrCroxx MrCroxx self-assigned this Dec 22, 2023
@github-actions github-actions bot added this to the release-1.6 milestone Dec 22, 2023
@hzxa21
Copy link
Collaborator

hzxa21 commented Jan 9, 2024

Any findings?

@MrCroxx
Copy link
Contributor Author

MrCroxx commented Jan 10, 2024

Working on reproducing the workload with foyer-storage-bench tool, foyer-rs/foyer#253 .

Copy link
Contributor

This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.

@hzxa21
Copy link
Collaborator

hzxa21 commented Jun 13, 2024

@MrCroxx Is this issue resolved?

@MrCroxx
Copy link
Contributor Author

MrCroxx commented Jun 20, 2024

There is no observation with the new foyer engine, but the algorithm has not been changed.

I'm going to close the issue for now. It the bug appears again, feel free to reopen it.

@MrCroxx MrCroxx closed this as completed Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-issue-activity type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants