Limit the DML memory to avoid frontend OOM

risingwavelabs / risingwave

Best-in-class stream processing, analytics, and management. Perform continuous analytics, or build event-driven applications, real-time ETL pipelines, and feature stores in minutes. Unified streaming and batch. PostgreSQL compatible.

https://go.risingwave.com/slack

Apache License 2.0

7.02k stars 577 forks source link

Limit the DML memory to avoid frontend OOM #16020

Open cyliu0 opened 7 months ago

cyliu0 commented 7 months ago

Is your feature request related to a problem? Please describe.

The frontend node will be OOM during ch-benchmark test loading data. https://buildkite.com/risingwave-test/ch-benchmark-risingwave/builds/17#018e7b25-ca57-4dcb-9792-2edb10740004

@chenzl25 suggest we could limit the memory of DML execution to reduce the frontend OOM.

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

github-actions[bot] commented 3 months ago

This issue has been open for 60 days with no activity.

If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean. Don't worry if you think the issue is still valuable to continue in the future. It's searchable and can be reopened when it's time. 😄