Hi Andrey, Thank you for your time. There's anything I can do to prevent this situation? Commit more often will help?
Vitor, terça-feira, 21 de Abril de 2015 às 20:16:42 UTC+1, Andrey Lomakin escreveu: > > Hi Vitor, > It means that you filled up write cache during migration and ti is flushed > synchronously to the disk , and you should wait a bit till the end of the > flush before next write operation will be performed. > > On Tue, Apr 21, 2015 at 7:39 PM, Vitor Enes Duarte <[email protected] > <javascript:>> wrote: > >> Hi, >> >> I'm working on a process to import from a MySQL database (I'm aware of >> OrientDB ETL but some data as to be pre processed before being inserted in >> OrientDB). >> At some point I'm getting this logs: >> Max cache limit is reached (3000 vs. 3001), sync flush is performed. >> Max cache limit is reached (3000 vs. 3001), sync flush is performed. >> Max cache limit is reached (3000 vs. 3002), sync flush is performed. >> ... >> >> I've see this <https://github.com/orientechnologies/orientdb/issues/3412> >> but I could understand if this is an issue or even what it means. >> >> Thank you for you help, >> >> >> Vitor, >> >> -- >> >> --- >> 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. > > -- --- 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.
