[flink] Respect low filesystem rate limits in remove_orphan_files

Open Beginner friendly
#4,320 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
java

Research direction

Locate the remove_orphan_files implementation and trace how the configured total filesystem rate is assigned across scan subtasks. Check the existing rate-limiting tests or add coverage for a total rate below the scan parallelism; done means fractional per-subtask rates preserve the requested aggregate best-effort limit.

Written by the indexing model from the issue text.

Description

Search before asking
  • I searched in the issues and found nothing similar.
Fluss version

0.9.0 (latest release)

Please describe the bug 🐞

remove_orphan_files assigns each scan subtask a minimum filesystem operation rate of 1/s. When the scan parallelism exceeds the configured total rate, this increases the aggregate rate above the requested limit.

For example, a total rate of 3 operations/s with parallelism 8 results in an aggregate target of 8 operations/s.

Solution

Allow fractional per-subtask rates by dividing the configured total rate by the scan parallelism, while retaining the existing best-effort rate-limiting semantics.

Are you willing to submit a PR?
  • I'm willing to submit a PR!
Dominant language
Java
Stars
2.2k
Forks
628
Avg merge
1d 19h
Merged PRs (30d)
138

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/fluss

All issues in apache/fluss

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.