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

[Enhancement] Reduce the memory usage during data ingestion #47047

Merged
merged 4 commits into from
Jun 17, 2024

Conversation

sevev
Copy link
Contributor

@sevev sevev commented Jun 14, 2024

Why I'm doing:

FE will send full schema to BE during data ingestion and each tablet may generate the new tablet schema according to the schema from FE and each delta_writer will keep a full schema until ingestion finished. If there are a lot of ingestion task and tablets, it maybe use a lot of memory.

What I'm doing:

The full schema for each delta_writer is no need to hold during the whole ingestion. We only need it during initialization, so we can release memory in advance.

Fixes #issue

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 3.3
    • 3.2
    • 3.1
    • 3.0
    • 2.5

Signed-off-by: sevev <qiangzh95@gmail.com>
@sevev sevev requested review from a team as code owners June 14, 2024 18:18
@mergify mergify bot assigned sevev Jun 14, 2024
Signed-off-by: sevev <qiangzh95@gmail.com>
POlapTableSchemaParam ptable_schema_param;
// `ptable_schema_param` is valid during initialization.
// And it may become invalid after initialization, so please do not access it afterward.
const POlapTableSchemaParam* ptable_schema_param = nullptr;
Copy link
Contributor

Choose a reason for hiding this comment

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

If this will be invalid after unit, why not make it a function variable in unit rather than store it in member variable.
And it will be better to set it to null after unit then it will cause crash rather than wild pointer issues

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If this will be invalid after unit, why not make it a function variable in unit rather than store it in member variable. And it will be better to set it to null after unit then it will cause crash rather than wild pointer issues

Actually this point is valid during data ingestion right now, but I worry that someone else might prematurely release the corresponding memory when making changes, so I added some comments as a warning. And we only need to access this memory during initialization. I reset it to nullptr after init and modified some comments to make it clearer for others to understand.

Signed-off-by: sevev <qiangzh95@gmail.com>
be/src/storage/delta_writer.h Outdated Show resolved Hide resolved
be/src/storage/delta_writer.cpp Outdated Show resolved Hide resolved
Signed-off-by: sevev <qiangzh95@gmail.com>
@wyb wyb enabled auto-merge (squash) June 17, 2024 03:40
Copy link

[FE Incremental Coverage Report]

pass : 0 / 0 (0%)

Copy link

[BE Incremental Coverage Report]

pass : 17 / 17 (100.00%)

file detail

path covered_line new_line coverage not_covered_line_detail
🔵 be/src/storage/delta_writer.cpp 15 15 100.00% []
🔵 be/src/runtime/local_tablets_channel.cpp 2 2 100.00% []

@wyb wyb merged commit 920c820 into StarRocks:main Jun 17, 2024
52 checks passed
Copy link

@Mergifyio backport branch-3.3

@github-actions github-actions bot removed the 3.3 label Jun 17, 2024
Copy link

@Mergifyio backport branch-3.2

@github-actions github-actions bot removed the 3.2 label Jun 17, 2024
Copy link
Contributor

mergify bot commented Jun 17, 2024

backport branch-3.3

✅ Backports have been created

Copy link
Contributor

mergify bot commented Jun 17, 2024

backport branch-3.2

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Jun 17, 2024
Signed-off-by: sevev <qiangzh95@gmail.com>
(cherry picked from commit 920c820)
mergify bot pushed a commit that referenced this pull request Jun 17, 2024
Signed-off-by: sevev <qiangzh95@gmail.com>
(cherry picked from commit 920c820)

# Conflicts:
#	be/src/storage/delta_writer.cpp
wanpengfei-git pushed a commit that referenced this pull request Jun 17, 2024
wanpengfei-git pushed a commit that referenced this pull request Jun 17, 2024
…47047) (#47086)

Signed-off-by: sevev <qiangzh95@gmail.com>
Co-authored-by: zhangqiang <qiangzh95@gmail.com>
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.

5 participants