We finally found the issue. The two links in my original email lead me to believe it was with Java 8. It is not.
This rocksdb issue https://github.com/facebook/rocksdb/issues/606 was very useful in helping to diagnose this. We have an artifactory server caching our jars from the main maven repo. The rocksdbjni.jar did NOT contain the snappy library compiled into it. The one we redownloaded from the central maven repo DOES. They way to tell is to run: nm librocksdbjni-linux64.so | grep snappy Hopefully this helps someone someday. Louis On 5/18/16, 11:25 AM, "Jason Erickson" <ja...@stormpath.com> wrote: >We have had this issue, too. Did you only see the issue when you migrated >to Java 8, or did you migrate to Java 8 and Samza 0.10 at the same time? > >On Tue, May 17, 2016 at 12:09 PM Louis Calisi <lcal...@tripadvisor.com> >wrote: > >> Hi, >> >> We are upgrading our pre-production environment to Java 8 and Samza 0.10. >> We are using Centos for our server. I’m running into this error: >> >> org.rocksdb.RocksDBException: Invalid argument: Compression type Snappy is >> not linked with the binary. >> >> I’ve seen this error before on the mailing lists: >> >> https://mail-archives.apache.org/mod_mbox/samza-dev/201602.mbox/%3CCAPs-oNugP8=1d_zea0giyophwclr_j9etvrvpmp0pc3vqi8...@mail.gmail.com%3E >> and >> https://issues.apache.org/jira/browse/SAMZA-870 >> >> Has this issue been resolved? Is Java 8 not a recommended JDK to run Samza >> (RocksDB with)? >> >> >> Thanks, Louis Calisi >> >> >> >>
