New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Java] Fix memory leaks in disabled Flight tests #38318
Comments
take |
jduo
added a commit
to Bit-Quill/arrow
that referenced
this issue
Nov 14, 2023
- Enable tests that were disabled due to flakey memory leaks - Explicitly close child allocators in these tests to match the behavior of FlightServerTestRule which does not leak.
jduo
added a commit
to Bit-Quill/arrow
that referenced
this issue
Nov 14, 2023
- Enable tests that were disabled due to flakey memory leaks - Explicitly close child allocators in these tests to match the behavior of FlightServerTestRule which does not leak. - Change TestBasicAuth to allocate only one server - Change TestBasicAuth2 to allocate only one server and client - Fix a bug in testAuth2#asyncPut() not including credentials
lidavidm
pushed a commit
that referenced
this issue
Nov 15, 2023
### Rationale for this change This enables tests that are currently disabled to improve coverage and help others build tests based on these. ### What changes are included in this PR? - Enable tests that were disabled due to flakey memory leaks - Explicitly close child allocators in these tests to match the behavior of FlightServerTestRule which does not leak. - Change TestBasicAuth to allocate only one server - Change TestBasicAuth2 to allocate only one server and client - Fix a bug in testBasucAuth2#asyncPut() not including credentials ### Are these changes tested? Tested locally. ### Are there any user-facing changes? No. * Closes: #38318 Authored-by: James Duong <james.duong@improving.com> Signed-off-by: David Li <li.davidm96@gmail.com>
lidavidm
changed the title
Fix memory leaks in disabled Flight tests
[Java] Fix memory leaks in disabled Flight tests
Nov 15, 2023
dgreiss
pushed a commit
to dgreiss/arrow
that referenced
this issue
Feb 19, 2024
) ### Rationale for this change This enables tests that are currently disabled to improve coverage and help others build tests based on these. ### What changes are included in this PR? - Enable tests that were disabled due to flakey memory leaks - Explicitly close child allocators in these tests to match the behavior of FlightServerTestRule which does not leak. - Change TestBasicAuth to allocate only one server - Change TestBasicAuth2 to allocate only one server and client - Fix a bug in testBasucAuth2#asyncPut() not including credentials ### Are these changes tested? Tested locally. ### Are there any user-facing changes? No. * Closes: apache#38318 Authored-by: James Duong <james.duong@improving.com> Signed-off-by: David Li <li.davidm96@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug, including details regarding any error messages, version, and platform.
A few tests in the Arrow Flight packages are flaky and leak memory when closing the BufferAllocator.
See #6392 and #38268
These tests have been disabled but should be re-enabled once a fix is made.
The memory leak may be due to the FlightServer not completing its shutdown process. The call to FlightServer#close() only blocks for 6 seconds and may leak memory if that timeout gets exceeded.
Component(s)
Java
The text was updated successfully, but these errors were encountered: