[lake/tiering] Continue claiming tables while readers remain idle
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 64/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- java
调研方向
Start at TieringSourceEnumerator.generateAndAssignSplits() and trace how split assignment, pending splits, reader availability, table claims, backoff, and concurrency limits interact. Reproduce the described A/B scenario, then add coverage showing B is claimed while readers remain idle, without completing A or advancing the periodic timer; verify empty responses and failures retain their backoff behavior.
由索引模型根据 Issue 内容生成。
描述
Motivation
After generating splits for a non-empty table, TieringSourceEnumerator.generateAndAssignSplits() assigns them and returns. If all pending splits were assigned but some readers are still waiting, it does not immediately claim another table.
Example: eight readers have already requested work and are waiting. A periodic poll claims table A with two splits, while table B is also available. After assigning A, six readers remain idle until another event or periodic poll triggers a claim. The default polling interval is 30 seconds; an earlier split completion can shorten this wait.
This is a scheduling gap identified by code inspection, separate from continuation after an empty table.
Solution
After assignment, asynchronously continue claiming tables while readers remain available and the pending split queue is empty. Stop when no table is available or the concurrency limit is reached. Coalesce claim requests and retain backoff for empty responses and failures.
Add a test for the example above: B should be assigned without completing A's splits or advancing the periodic timer. Do not buffer extra splits on busy readers.
Anything else?
Related: #4372 addresses empty tables. This case concerns non-empty tables whose splits do not fill the waiting readers.
Willingness to contribute
- I'm willing to submit a PR!
- 主要语言
- Java
- 星标
- 2.2k
- 派生
- 656
- 平均合并
- 1 天 21 小时
- 30 天内合并 PR
- 127
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
apache/fluss 的其他 Issue
-
[lake/iceberg] Reserved write-mode properties can be set and reset through their `iceberg.` key可能已有人在做 @aphenix-r7 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
[common] Decimal#hashCode is inconsistent with Decimal#equals可能已有人在做 @firasbouzazi 于 13 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
[security] PlainSaslServerProvider conflicts with Hadoop SASL provider causing authentication failure可能已有人在做 @xinzhang-hello 于 19 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
[server] KV snapshot scheduling stops permanently after a transient snapshot-init failure可能已有人在做 @zhang-arvin 于 19 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
[docs] Document advertised-resource and ACL principal ignore-case options可能已有人在做 @EchoLee5 于 31 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 90/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
apache/rocketmq-dashboard#6896 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 67/100
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
OpenIntegrationEngine/engine#496 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 76/100
SasanLabs/VulnerableApp#836 ·
维护者通常 1 天内回复