Yeah that sounds pretty much okay. But it should actually look if data is actually corrupt. I didn't touch the data and was just reading it. So it might be taken into memory but not changed. From my perspective there was no need for rebuilding an index. But if there actually is, okay, so I now know to have an eye on shutting down the server correctly.
Am Mittwoch, 10. September 2014 10:36:07 UTC+2 schrieb Andrey Lomakin: > > Hi, > To speed up data processing data are cached in memory in write and read > cache, if you do not flush cache correctly (it is the same as discarding > flash storage from windows usb port) it can lead to data corruption. > To avoid data corruption we use wal where all operations are logged. > So we restore data from wal and then rebuild indexes. > > > On Wed, Sep 10, 2014 at 11:14 AM, 'Curtis Mosters' via OrientDB < > [email protected] <javascript:>> wrote: > >> So from time to time I backup the AWS server. And sometimes forgetting to >> crrectly shutdown the server. >> >> So when the AWS server is up again and starting OrientDB server it needs >> to rebuild the index. >> >> But why? Could someone tell me what I can do against it. I don't know why >> a rebuild is needed. The data is stored in files. How can they be harmed >> after a server was not correctly shutdowned. >> >> Thanks. >> >> -- >> >> --- >> 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] <javascript:>. >> 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.
