We realized that the snappy library was causing problems, so we switched to 'nothing' compression.
Here are our server settings: <entry name="tx.useLog" value="true" /> <entry name="tx.log.fileType" value="classic" /> <entry name="tx.log.synch" value="true" /> <entry name="tx.commit.synch" value="true" /> <entry name="tx.autoRetry" value="20" /> <entry name="index.txMode" value="FULL" /> <entry name="index.durableInNonTxMode" value="true" /> <entry name="storage.compressionMethod" value="nothing" /> <entry name="record.downsizing.enabled" value="false" /> <entry name="nonTX.recordUpdate.synch" value="true" /> <entry name="storage.wal.maxSize" value="500" /> <!-- size is in MB --> Steve On Thursday, June 12, 2014 11:37:40 AM UTC-6, Andrey Lomakin wrote: > > Hi Steven, > > About last errors corrupt literal length and serialization errors, it is > related to old Snappy library, could you migrate to 1.7 version or to gzip > to solve it ? > > This error "Can not restore 1 WAL master record for storage" is > waring you can skip it. > > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
