Now that 2.0 is being pushed out, is there anyway this could be put into a sooner release. We have some customers who've built up 30GB of wal files. Telling them they have to reboot their system is not a very attractive solution for them.
Thanks. On Monday, December 9, 2013 5:20:10 AM UTC-6, Andrey Lomakin wrote: > > Oh guys sorry, > It is partially fixed in 1.6.2 and will be fixed in 2.0, when write ahead > log will be automatically truncated. > > > On Mon, Dec 9, 2013 at 1:05 PM, Sylvain Spinelli > <[email protected]<javascript:> > > wrote: > >> up. >> Seems an annoying issue for us before we plan to migrate from local to >> plocal. >> What are the plans on this point ? >> >> Sylvain >> >> >> Le 04/12/2013 22:43, StevenTomer a écrit : >> >> I'm using a database with plocal storage, and the .wal files created in >> the database directory are starting to pile up (12 GB). There's about 350 >> of them right now. >> >> Is this expected? It seems like they should be cleaned up. >> >> What can I do to minimize this? >> >> Steve >> -- >> >> >> -- >> >> --- >> 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/groups/opt_out. >> > > > > -- > 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/groups/opt_out.
