In 2.0.2.1: exception during load of embedded cassandra

[fkoehler]

When running

EmbeddedCassandraServerHelper.startEmbeddedCassandra

in version 2.0.2.1 we get the exception:

[error] o.a.c.c.QueryProcessor - Unable to initialize MemoryMeter (jamm not specified as javaagent).  This means Cassandra will be unable to measure object sizes accurately and may consequently OOM.
[error] o.a.c.s.CassandraDaemon - Exception in thread Thread[CompactionExecutor:3,1,main]
java.lang.NoSuchMethodError: com.google.common.util.concurrent.RateLimiter.acquire(I)V
    at org.apache.cassandra.io.compress.CompressedThrottledReader.reBuffer(CompressedThrottledReader.java:40) ~[cassandra-all-2.0.5.jar:2.0.5]
    at org.apache.cassandra.io.util.RandomAccessReader.seek(RandomAccessReader.java:280) ~[cassandra-all-2.0.5.jar:2.0.5]
    at org.apache.cassandra.io.sstable.SSTableScanner$KeyScanningIterator.computeNext(SSTableScanner.java:262) ~[cassandra-all-2.0.5.jar:2.0.5]
    at org.apache.cassandra.io.sstable.SSTableScanner$KeyScanningIterator.computeNext(SSTableScanner.java:203) ~[cassandra-all-2.0.5.jar:2.0.5]
    at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) ~[guava-16.0.1.jar:na]
    at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) ~[guava-16.0.1.jar:na]

[rsertelon]

This is due to Guava's version. You might have a version that is > 15.0, which leads to this problem.

Indeed, the Guava team has modified the return type of the acquire method in 16.0, thus your problem.

I've stumble upon the same problem, and the only things I think about to solve this problem is either:

• Downgrade Guava to 15.0
• Update Cassandra to 2.1.0 (they updated to Guava 16.0, so it should be compatible with 18.0 for this particular method)

I've personnaly tried the second, as I use recent features of Guava.

I'm currently trying to make it work on my side (forked the project), but as I said, this would require to run tests on Cassandra 2.1.X, and I don't know to what extent this could be a problem (compared to testing on 2.0.X).

[rsertelon]

Hi @fkoehler,

If you still need an answer to this problem, the latest snapshot of cassandra-unit contains a fix for this problem. (See #92)

[fkoehler]

hi! we are not currently using it anymore, we resorted back to a normal
installation but thanks for fixing this!

2014-09-26 19:24 GMT+02:00 Romain Sertelon notifications@github.com:

Hi @fkoehler https://github.com/fkoehler,

If you still need an answer to this problem, the latest snapshot of
cassandra-unit contains a fix for this problem. (See #92
#92)

—
Reply to this email directly or view it on GitHub
#84 (comment)
.

[rsertelon]

Okay :) @jsevellec I think this issue can be closed ;)