[ https://issues.apache.org/jira/browse/ARROW-9586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Li resolved ARROW-9586. ----------------------------- Resolution: Fixed Issue resolved by pull request 8265 [https://github.com/apache/arrow/pull/8265] > [FlightRPC][Java] Allow using a per-call Arrow allocator > -------------------------------------------------------- > > Key: ARROW-9586 > URL: https://issues.apache.org/jira/browse/ARROW-9586 > Project: Apache Arrow > Issue Type: Improvement > Components: FlightRPC, Java > Reporter: David Li > Assignee: David Li > Priority: Major > Labels: pull-request-available > Fix For: 4.0.0 > > Time Spent: 4.5h > Remaining Estimate: 0h > > 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. -- This message was sent by Atlassian Jira (v8.3.4#803005)