cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Steinmaurer (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8685) Consider upgrade to thrift 0.9.2 (or later)
Date Thu, 29 Jan 2015 18:47:35 GMT


Thomas Steinmaurer commented on CASSANDRA-8685:

Can you drop this in without re-compiling?

* Stopping Cassandra 2.0.11
* Replacing thrift library 0.9.1 with 0.9.2
* Starting Cassandra 2.0.11

Haven't seen any sign of troubles in the Cassandra log or Astyanax based log in our application.
To be honest I had hoped that it will be considered even for 2.0.x public. I have no idea
about other users roadmap regarding 2.1 in production, but we are moving from 1.2.15 (DSE
3.2.5) to 2.0.11 (DSE 4.5.3) in production soon and will settle with 2.0 for at least this
year I guess.

Anyway, thanks for your swift reply here!

> Consider upgrade to thrift 0.9.2 (or later)
> -------------------------------------------
>                 Key: CASSANDRA-8685
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Adam Hattrell
>            Assignee: T Jake Luciani
>             Fix For: 2.1.3
>         Attachments: thrift1457fix_cassandra_heap.png, thrift1457fix_cassandra_heap_framedtransport.png
> Folks using Astyanax and the like are subject to
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

View raw message