You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (JIRA)" <ji...@apache.org> on 2013/08/16 12:58:05 UTC

[jira] [Updated] (CASSANDRA-5887) add lz4 compression for internode compressio

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

Marcus Eriksson updated CASSANDRA-5887:
---------------------------------------

    Attachment: 0001-compress-internode-traffic-with-lz4-v1.patch

uses lz4 to compress internode traffic

patch is large since it upgrades the lz4 lib to the latest version. The one shipped only did "async flush" - meaning it didnt actually flush all the data.
                
> add lz4 compression for internode compressio
> --------------------------------------------
>
>                 Key: CASSANDRA-5887
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5887
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Andy Cobley
>            Assignee: Marcus Eriksson
>            Priority: Minor
>         Attachments: 0001-compress-internode-traffic-with-lz4-v1.patch
>
>
> Currently when internode compression is turned on it uses snappy.SnappyOutputStream.  If Snappy is not available this will fail.  lz4 compression is vetted for use in Cassandra.  Would it make sense to use lz4 for internode compression ?  Would a new config setting internode_compressor be needed for compatibility ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira