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

[flink] Introduce fine-grained options to increase Committer heap memory only #1986

Merged
merged 2 commits into from
Sep 13, 2023

Conversation

JingsongLi
Copy link
Contributor

@JingsongLi JingsongLi commented Sep 12, 2023

Purpose

Committer node may use a large memory if the amount of data written to the table is particularly large, OOM may occur
if the memory is too small. In this case, you need to increase the Committer heap memory, but you may not want to
increase the memory of Flink's TaskManager uniformly, which may lead to a waste of memory.

You can use fine-grained-resource-management of Flink to increase committer heap memory only:

  1. Configure Flink Configuration cluster.fine-grained-resource-management.enabled: true. (This is default after Flink 1.18)
  2. Configure Paimon Table Options: sink.committer-cpu (for example 1.0) and sink.committer-memory (for example 300 MB, depends on your TaskManager).

Tests

API and Format

Documentation

@JingsongLi JingsongLi changed the title [flink] Introduce fine-grained options to increase Committer heap mem… [flink] Introduce fine-grained options to increase Committer heap memory only Sep 12, 2023
Copy link
Contributor

@yuzelin yuzelin left a comment

Choose a reason for hiding this comment

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

+1

@JingsongLi JingsongLi merged commit e4224a1 into apache:master Sep 13, 2023
9 checks passed
schnappi17 pushed a commit to schnappi17/flink-table-store that referenced this pull request Sep 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants