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

feat(memory): Separate total memory configurations for FE and Compactor #19372

Merged
merged 7 commits into from
Nov 15, 2024

Conversation

Li0k
Copy link
Contributor

@Li0k Li0k commented Nov 13, 2024

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

What's changed and what's your intention?

part of #19245

This PR introduces a separate total memory configuration for FE and Compactor.

In standalone deployment mode, the total_memory of different nodes should be set to achieve memory isolation. (Not included in this PR)

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.

@Li0k Li0k requested review from hzxa21, chenzl25 and kwannoel November 13, 2024 07:41
@Li0k Li0k marked this pull request as ready for review November 13, 2024 07:42
Copy link
Contributor

@chenzl25 chenzl25 left a comment

Choose a reason for hiding this comment

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

LGTM

src/frontend/src/lib.rs Outdated Show resolved Hide resolved
@@ -159,6 +160,10 @@ pub struct FrontendOpts {
default_value = "./secrets"
)]
pub temp_secret_file_dir: String,

/// Total available memory for the frontend node in bytes. Used by both computing and storage.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
/// Total available memory for the frontend node in bytes. Used by both computing and storage.
/// Total available memory for the frontend node in bytes. Used by frontend.

Copy link
Collaborator

Choose a reason for hiding this comment

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

I think this comment is not resolved.

Copy link
Contributor

@kwannoel kwannoel left a comment

Choose a reason for hiding this comment

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

Generally LGTM, thanks for your work in debugging this and providing a solution!

@Li0k Li0k enabled auto-merge November 14, 2024 08:13
@Li0k Li0k added this pull request to the merge queue Nov 15, 2024
Merged via the queue into main with commit 4085f56 Nov 15, 2024
28 of 29 checks passed
@Li0k Li0k deleted the li0k/memory_calculation branch November 15, 2024 09:28
@hzxa21
Copy link
Collaborator

hzxa21 commented Nov 19, 2024

Should we cherry pick this to 2.1?

@@ -159,6 +160,10 @@ pub struct FrontendOpts {
default_value = "./secrets"
)]
pub temp_secret_file_dir: String,

/// Total available memory for the frontend node in bytes. Used by both computing and storage.
Copy link
Member

Choose a reason for hiding this comment

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

Does storage run in frontend? IIRC, even in local execution mode, the TableScan is pushed to compute nodes.

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.

6 participants