I'm getting a org.xerial.snappy.SnappyError when creating my first column
family after blowing away my Cassandra installation and trying to run the
latest release. I'm undoubtably making some silly mistake but cannot seem
to find it. I even commented out my sstable_compression=SnappyCompressor
Reverting to JDK 1.6 appears to fix the issue. Is JDK 1.7 not yet supported
by Cassandra?
java version 1.6.0_31
Java(TM) SE Runtime Environment (build 1.6.0_31-b04-415-11M3635)
Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01-415, mixed mode)
On Tue, May 15, 2012 at 12:55 PM, Stephen McKamey
I just received an email from AWS about rebooting my EC2 instance for
maintenance. Thankfully this is just my webhead, but I'm
curious have others experienced this with a Cassandra instance?
http://aws.amazon.com/maintenance-help/
The details seem to say that if you allow them to do the reboot
I'm curious about Expiring Columns. Say I create a Column Family where *all*
of the Columns are set to be expiring columns. When a row's entire set of
columns have expired, will an empty row it sill be returned in range
queries? Or will it just be nicely compacted away?
[I wrote this Apr 10, 2011 at 12:09 but my message seems to have gotten lost
along the way.]
I use Pelops (the 1.0-0.7.x build from the Github Maven repo) and have
occasionally seen this message (under load or during GC). I have a test app
running in two separate single-threaded processes doing a
