Re: sstable_compression for system tables

2013-05-03 Thread John Sanda
The root cause was as I described. System tables were creating while running OpenJDK. Files were written to disk using snappy compression. Cassandra was later restarted with IBM Java. With the IBM JRE on a 32 bit arch, the native snappy library is not found; consequently, Cassandra is not able to r

Re: sstable_compression for system tables

2013-05-03 Thread Robert Coli
On Fri, May 3, 2013 at 11:07 AM, John Sanda wrote: > The machine where this error occurred had both OpenJDK and IBM's Java > installed. The only way I have been able to reproduce is by installing > Cassandra with OpenJDK, shutting it down, the starting it back up with IBM > Java. Maybe the root c

Re: sstable_compression for system tables

2013-05-03 Thread John Sanda
The machine where this error occurred had both OpenJDK and IBM's Java installed. The only way I have been able to reproduce is by installing Cassandra with OpenJDK, shutting it down, the starting it back up with IBM Java. Snappy compression is enabled with OpenJDK so SSTables, including for system

Re: sstable_compression for system tables

2013-05-03 Thread John Sanda
I am still trying to sort this out. When I run with Oracle's JRE, it does in fact look like compression is enabled for system tables. cqlsh> DESCRIBE TABLE system.schema_columnfamilies ; CREATE TABLE schema_columnfamilies ( keyspace_name text, columnfamily_name text, bloom_filter_fp_chance

Re: sstable_compression for system tables

2013-05-03 Thread Edward Capriolo
I did not know the system tables were compressed. That would seem like an odd decision you would think that the system tables are small and would not benefit from compression much. Is it a static object static object that requires initialization even though it is not used? On Fri, May 3, 2013 at