Hi, Could you post a few full thread dumps? I guess it's a bug in the MVStore compaction, which goes into an (almost) endless loop for some reason. I got reports of similar behavior, and I'm working on this now. Unfortunately, currently there is no way to configure it from with the database engine (you can disable it from the MVStore.Builder API: autoCompactFillRate(0), but there is no config option in the database URL yet). So if this is the problem, the workaround is to disable the MVStore, by appending ";MV_STORE=FALSE" to the database URL.
Regards, Thomas On Sun, Dec 7, 2014 at 9:17 AM, Stephen Lake <[email protected]> wrote: > A couple of things to add. This high processor usage stops after about > three hours. I am really struggling to understand what is going on here. > Is it possibly updating the index's for three hours after the original > dump of rows into he database? I can see there is a LOT if garbage > collection going on. > > Regards > > Stephen. > > -- > You received this message because you are subscribed to the Google Groups > "H2 Database" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/h2-database. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
