apache/fluss

Paimon tiering best practise note in docs

Open

#1,306 opened on Jul 11, 2025

View on GitHub
 (1 comment) (3 reactions) (1 assignee)Java (570 forks)auto 404
component=docsgood first issue

Repository metrics

Stars
 (1,979 stars)
PR merge metrics
 (PR metrics pending)

Description

Search before asking

  • I searched in the issues and found nothing similar.

Description

When users use the tiering service to write to paimon, parquet writers use Flink memory however managed memory is not used. Users can set the managed.memory to a small value like 128MB or lower and give that memory back to the JVM heap, to avoid wasting resources.

We can add this as a "best practices section" when starting the tiering service.

Willingness to contribute

  • I'm willing to submit a PR!

Contributor guide

Research direction
Add a best practices section in the tiering service documentation explaining that managed.memory can be set low when using Paimon tiering with Parquet writers, as Parquet writers use Flink memory.
Tech stack
java
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85