[FlightRPC][Java] Allow using a per-call Arrow allocator
- Lenguaje dominante
- Java
- Estrellas
- 94
- Forks
- 152
- Merge medio
- 3 d 16 h
- PR fusionados (30 d)
- 11
Descripción
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.*
Guía de contribución
Línea de trabajo
Comienza revisando la implementación de flight-grpc y las dos pull requests enlazadas para entender el enfoque propuesto. Verifica que cada llamada DoGet/DoPut pueda usar un asignador secundario de Arrow y que todos los recursos de Arrow se liberen antes de notificar a gRPC que la llamada ha terminado.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- grpc, java
- Área
- api, backend
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 25/100