[FlightRPC][Java] Allow using a per-call Arrow allocator
- 主要語言
- Java
- 星號
- 94
- 分支
- 152
- 平均合併
- 3 天 16 小時
- 30 天內合併 PR
- 11
描述
We've been running into issues with Flight and gRPC leaking direct memory at scale. One thing we'd like to do is have a (child) allocator per DoGet/DoPut call, so we can more accurately track memory usage. We have a candidate implementation that is rather messy, but can be upstreamed as part of flight-grpc.
This also requires changes to _ensure_ all Arrow resources are cleaned up before we notify gRPC that the call has finished.
**Reporter**: [David Li](https://issues.apache.org/jira/browse/ARROW-9586) / @lidavidm
#### PRs and other links:
- [GitHub Pull Request apache/arrow#8265](https://github.com/apache/arrow/pull/8265)
- [GitHub Pull Request apache/arrow#9417](https://github.com/apache/arrow/pull/9417)
**Note**: *This issue was originally created as [ARROW-9586](https://issues.apache.org/jira/browse/ARROW-9586). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
貢獻指南
研究方向
先檢視 flight-grpc 實作和連結的兩個 pull request,以了解候選方案。確認每個 DoGet/DoPut 呼叫都能使用子 Arrow 配置器,並且在通知 gRPC 呼叫已完成之前,所有 Arrow 資源都已清理完畢。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- grpc, java
- 領域
- api, backend
- Issue 類型
- 功能
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 25/100