Details
-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
2.2.2
Description
Problem:
There is an upstream bug in Netty whereby the maxCapacity parameter for the Recycler is not honored under certain usage patterns with the Java SDK. The result is a slow, but gradual memory leak. It has also been observed that the hardcoded default value of 262144 is not honored within Netty as well.
A current workaround is to set the maxCapacity parameter to 0 and disable the Recycler:
-Dcom.couchbase.client.deps.io.netty.recycler.maxCapacity=0
|
Request:
As the Couchbase Java SDK leverages Netty, we should find a way to help resolve this issue in Netty.
Attachments
Issue Links
- links to