First of all - it has nothing to do with disk space available. It is a bug in MVStore. When chunk is saved and insufficient space for chunk header is reserved at the beginning, but later when all chunk's data is written and it's time to write actual values into the header (and this is JSON-like formatted string with chunk attributes) it turn's out that reserved space is insufficient. Your massive entries removal indded may trigger that. Latest version (1.4.200) does more conservative estimate, so chance of this happening is reduced, but not eliminated. We just need to handle that condition in a more robust way (it is totally recoverable), instead of throwing the towel.
As far as automatic reopening goes - it not always a good idea, because root cause for premature closure could be anything. If you think that you need that, it can be easily implemented by application. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/2a231bda-7be1-484d-8e30-edf43c20cee9%40googlegroups.com.
