Uploaded image for project: 'Couchbase Java Client'
  1. Couchbase Java Client
  2. JCBC-951

Upstream Netty Bug 4146 - Recycler MaxCapacity parameter value not honored

    XMLWordPrintable

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.2.2
    • None
    • Dependencies

    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

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            Michael Nitschinger: we had targeted this for 2.4 at some point I think, which is how it got the sdk-46 label.  Is that still valid, or something further out?  Please adjust the label as needed.

            ingenthr Matt Ingenthron added a comment - Michael Nitschinger : we had targeted this for 2.4 at some point I think, which is how it got the sdk-46 label.  Is that still valid, or something further out?  Please adjust the label as needed.

            People

              daschl Michael Nitschinger
              merrick.huang Merrick Huang (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty