cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3573) When Snappy compression is not available on the platform, trying to enable it introduces problems
Date Mon, 05 Dec 2011 18:26:40 GMT


Pavel Yaskevich commented on CASSANDRA-3573:

you are right, I will add validation to SnappyCompressor create method to ensure that Snappy
lib is in place.
> When Snappy compression is not available on the platform, trying to enable it introduces
> -------------------------------------------------------------------------------------------------
>                 Key: CASSANDRA-3573
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.0
>         Environment: FreeBSD
>            Reporter: Vitalii Tymchyshyn
>            Assignee: Pavel Yaskevich
>            Priority: Minor
>             Fix For: 1.0.6
>         Attachments: CASSANDRA-3573.patch
> I've tried to enable compression for some column families in my cluster using Snappy
> It does not work and I am having problems with schema updates to remove it (a lot of
UNREACHABLE nodes during scema update).
> In log I have the next:
> ERROR [FlushWriter:961] 2011-12-05 17:16:33,383 (line 133)
Fatal exception in thread Thread[Flu
> shWriter:961,5,main]
> java.lang.NoClassDefFoundError: Could not initialize class org.xerial.snappy.Snappy
>         at
>         at<init>(
>         at
>         at<init>(
>         at org.apache.cassandra.db.ColumnFamilyStore.createFlushWriter(
>         at org.apache.cassandra.db.Memtable.writeSortedContents(
>         at org.apache.cassandra.db.Memtable.access$400(
>         at org.apache.cassandra.db.Memtable$4.runMayThrow(
>         at
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at
> It looks like Snappy can't initialize because it does not have native library for my
platform. It would be great if:
> 1) A check be done on schema update if Snappy can be used
> 2) If it is enabled and can't be used it would still work without compression writes
(but may be outputting some errors to indicate the situation)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message