[
https://issues.apache.org/jira/browse/ARROW-9586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197302#comment-17197302
]
David Li commented on ARROW-9586:
---------------------------------
I will try to get to this for 2.0 but it may not make it.
> [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
> Fix For: 2.0.0
>
>
> 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)
