Hi, you should not typical worry about it, we have 2 master records in operation log, if one is broken second one is used. Usually it only affects data restore after crash and you should worry about this exception if both master records will be broken.
Master records contain information of position in operation log from which data should be restored. On Sat, Aug 9, 2014 at 3:34 AM, Jing Chen <[email protected]> wrote: > Hi there, > > I noticed this error in the OrientDB server log today when I was loading > data to the database: > > 2014-08-08 11:09:42:355 SEVE Can not restore 0 WAL master record for > storage ndex crc check is failed [OWriteAheadLog] > > What does this error mean? Should I worry about the data being loaded? My > Java application connects to the server through a remote connection and > insert data to the database through Orientdb Graph API. I didn't get any > exception from my Java program during the insert. Should this error throw > an exception in the client? > > Thanks, > Jing > > -- > > --- > 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. Orient Technologies the Company behind OrientDB -- --- 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.
