You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Thomas Steinmaurer (JIRA)" <ji...@apache.org> on 2015/01/29 12:10:34 UTC

[jira] [Updated] (CASSANDRA-8685) Consider upgrade to thrift 0.9.2 (or later)

     [ https://issues.apache.org/jira/browse/CASSANDRA-8685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Steinmaurer updated CASSANDRA-8685:
------------------------------------------
    Attachment: thrift1457fix_cassandra_heap_framedtransport.png
                thrift1457fix_cassandra_heap.png

> Consider upgrade to thrift 0.9.2 (or later)
> -------------------------------------------
>
>                 Key: CASSANDRA-8685
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8685
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Adam Hattrell
>            Assignee: T Jake Luciani
>         Attachments: thrift1457fix_cassandra_heap.png, thrift1457fix_cassandra_heap_framedtransport.png
>
>
> Folks using Astyanax and the like are subject to  https://issues.apache.org/jira/browse/THRIFT-1457 and may run into heap pressure on the Cassandra side for larger read request, as thrift doesn't reset its internal buffer.  This can lead to larger TFramedTransport instances will be kept on the heap.
> I've seen at least one situation where this has saved around 1Gb of heap space on average.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)