Uploaded image for project: 'Thrift'
  1. Thrift
  2. THRIFT-1457

Capacity of TframedTransport write buffer is never reset

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.6.1
    • 0.9.2
    • Java - Library
    • None

    Description

      The writeBuffer_ instance variable of TframedTransport can only grow and is never reset to its original capacity. This causes memory issues for clients using a connection pool.

      The size of this buffer grows to 16MB in our application. With a connection pool of 50 connections, this leads to a loss up to 800MB.

      Attachments

        Issue Links

        is duplicated by

        Bug - A problem which impairs or prevents the functions of the product. THRIFT-3988 TFramedTransport's writeBuffer_ may cause the client OOM

        • Major - Major loss of function.
        • Closed

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            roger Roger Meier
            arthurm Arthur Meyer
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment