Hi, this message meant that wal found few problems and tries to restore itslef, you should not experience any problems in this case, even all master records will be broken, In such case data will be restored from beginning of WAL.
But seems shutdown.sh was prematurely closed, so you have timeout or something if server close is taking too long ? On Thu, Dec 11, 2014 at 3:54 PM, Simon L <[email protected]> wrote: > 2014-12-11 13:50:01:951 SEVERE Can not restore 0 WAL master record for > storage XXXXXX crc check is failed [ODiskWriteAheadLog] > > I got this error after a huge (multi-GB) import using the ETL... > - I shutdown the server properly with "shutdown.sh" > - OS: Ubuntu 14.04, on Amazon EC2, Java build 1.8.0_25-b17 > > So far, I don't see any issues, but maybe some data didn't import, or > perhaps I'll notice some later? > > Is it possible that shutdown.sh doesn't flush the write ahead log? > > -- > > --- > 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. > -- Best regards, Andrey Lomakin. -- --- 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.
