You can translate the question and the replies:

Problem with Amazon Athena Cache

Hello, We have Denodo VDP 8.0 running in a Linux server. We add Amazon Athena Cache and we have a problem when try to store results in cache. The logs registered: FATAL YYYY-MM-DDTHH:MI:SS.FFF com.denodo.vdb.engine.thread.ReusableThread [] - runWork - Unexpected error: Could not initialize class org.xerial.snappy.Snappy java.lang.NoClassDefFoundError: Could not initialize class org.xerial.snappy.Snappy at org.apache.parquet.hadoop.codec.SnappyCompressor.compress(SnappyCompressor.java:67) ~[parquet-hadoop.jar:1.11.0] at org.apache.hadoop.io.compress.CompressorStream.compress(CompressorStream.java:81) ~[hadoop-common.jar:?] at org.apache.hadoop.io.compress.CompressorStream.finish(CompressorStream.java:92) ~[hadoop-common.jar:?] at org.apache.parquet.hadoop.CodecFactory$HeapBytesCompressor.compress(CodecFactory.java:165) ~[parquet-hadoop.jar:1.11.0] at org.apache.parquet.hadoop.ColumnChunkPageWriteStore$ColumnChunkPageWriter.writePage(ColumnChunkPageWriteStore.java:122) ~[parquet-hadoop.jar:1.11.0] at org.apache.parquet.column.impl.ColumnWriterV1.writePage(ColumnWriterV1.java:53) ~[parquet-column.jar:1.11.0] at org.apache.parquet.column.impl.ColumnWriterBase.writePage(ColumnWriterBase.java:315) ~[parquet-column.jar:1.11.0] at org.apache.parquet.column.impl.ColumnWriteStoreBase.flush(ColumnWriteStoreBase.java:152) ~[parquet-column.jar:1.11.0] at org.apache.parquet.column.impl.ColumnWriteStoreV1.flush(ColumnWriteStoreV1.java:27) ~[parquet-column.jar:1.11.0] at org.apache.parquet.hadoop.InternalParquetRecordWriter.flushRowGroupToStore(InternalParquetRecordWriter.java:172) ~[parquet-hadoop.jar:1.11.0] at org.apache.parquet.hadoop.InternalParquetRecordWriter.close(InternalParquetRecordWriter.java:114) ~[parquet-hadoop.jar:1.11.0] at org.apache.parquet.hadoop.ParquetWriter.close(ParquetWriter.java:310) ~[parquet-hadoop.jar:1.11.0] at com.denodo.vdb.util.tablemanagement.sql.insertion.athena.AthenaAwsInsertWorker.onBlockFinish(Unknown Source) ~[denodo-vdp-server.jar:8.0.2] at com.denodo.vdb.util.tablemanagement.sql.insertion.DFInsertWorker.d3(Unknown Source) ~[denodo-vdp-server.jar:8.0.2] at com.denodo.vdb.util.tablemanagement.sql.insertion.DFInsertWorker.doRun(Unknown Source) ~[denodo-vdp-server.jar:8.0.2] at com.denodo.vdb.util.tablemanagement.sql.insertion.AbstractInsertionWorker.run(Unknown Source) ~[denodo-vdp-server.jar:8.0.2] at com.denodo.vdb.cache.jdbc.ViewDataStorer.doRun(Unknown Source) ~[denodo-vdp-server.jar:8.0.2] at com.denodo.vdb.engine.thread.AbstractWorker.run(Unknown Source) ~[denodo-vdp-server.jar:8.0.2] at com.denodo.vdb.engine.thread.WorkWrapper.a3(Unknown Source) ~[denodo-vdp-server.jar:8.0.2] at com.denodo.vdb.engine.thread.ReusableThread.d3(Unknown Source) [denodo-vdp-server.jar:8.0.2] at com.denodo.vdb.engine.thread.ReusableThread.run(Unknown Source) [denodo-vdp-server.jar:8.0.2] how can we solve this problem? Thanks!
user
03-02-2022 11:55:42 -0500

1 Answer

Hi, You are facing this error “*Could not initialize class org.xerial.snappy.Snappy java.lang.NoClassDefFoundError* '' due to an issue encountered while loading the *snappy-java.jar* library. On Linux platforms, this error occurs when the compression/decompression feature of Snappy library is enabled.The native library *snappy-<version>-libsnappyjava.so* for Snappy compression is included in the *snappy-java-<version>.jar* file. When the JVM initializes the JAR, the library is added to the default temp directory. If the default temp directory is mounted with the *noexec* option, it results in the above exception. Inorder to resolve this issue without disabling the compression feature of snappy, you can add the following JVM option to Denodo server to specify a different temp directory which is mounted without the *noexec* option. “-Dorg.xerial.snappy.tempdir=/path/to/newtmp” You can refer to the [Configuration of the JVM Parameters from the Command Line](https://community.denodo.com/docs/html/browse/8.0/en/platform/installation/denodo_platform_control_center/configuration_of_the_jvm_parameters_from_the_command_line/configuration_of_the_jvm_parameters_from_the_command_line) section of Denodo Platform Installation Guide to change the JVM Configuration. If you are a valid Support user and need more assistance on this topic, you could create a Support case and the Support team would assist you. Hope this helps!
Denodo Team
04-02-2022 07:00:37 -0500
You must sign in to add an answer. If you do not have an account, you can register here