-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Enable Netty 4 advanced leak detection in tests and fail the build if there is a leak #20398
Labels
Comments
jasontedor
added
>enhancement
:Distributed Coordination/Network
Http and internode communication implementations
labels
Sep 9, 2016
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this issue
Jul 6, 2018
* Enabled advanced leak detection when loading `EsTestCase` * Added custom `Appender` to collect leak logs and check for logged errors in a way similar to what is done for the `StatusLogger` * Fixes elastic#20398
Gave this a go in #31861 :) |
original-brownbear
added a commit
that referenced
this issue
Jul 20, 2018
* Enabled advanced leak detection when loading `EsTestCase` * Added custom `Appender` to collect leak logs and check for logged errors in a way similar to what is done for the `StatusLogger` * Fixes #20398
original-brownbear
added a commit
to original-brownbear/elasticsearch
that referenced
this issue
Jul 20, 2018
* Enabled advanced leak detection when loading `EsTestCase` * Added custom `Appender` to collect leak logs and check for logged errors in a way similar to what is done for the `StatusLogger` * Fixes elastic#20398
original-brownbear
added a commit
that referenced
this issue
Jul 20, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Netty has pooled and unpooled byte buf alloactors. The pooled allocator uses reference counting to track when a byte buf can be returned to the pool, and leak detection to ensure that byte bufs are properly accessed/released. Netty has different levels of detection from disabled to paranoid (check every access). We should enable leak detection in tests and fail the build if a leak is detected.
Relates #19526, relates #19562
The text was updated successfully, but these errors were encountered: