You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Roger Schildmeijer (JIRA)" <ji...@apache.org> on 2013/11/24 17:17:35 UTC

[jira] [Commented] (THRIFT-1457) Capacity of TframedTransport write buffer is never reset

    [ https://issues.apache.org/jira/browse/THRIFT-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13830965#comment-13830965 ] 

Roger Schildmeijer commented on THRIFT-1457:
--------------------------------------------

[~arthurm] did you manage to get around this? I've been bitten by this when using a popular Cassandra java client.



> Capacity of TframedTransport write buffer is never reset
> --------------------------------------------------------
>
>                 Key: THRIFT-1457
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1457
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Java - Library
>    Affects Versions: 0.6.1
>            Reporter: Arthur Meyer
>         Attachments: THRIFT-1457.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.1#6144)