On Wednesday, March 11, 2020 at 1:15:25 AM UTC, h2new wrote: > > Hello all, > > we are using H2 in our java application. > For a while I am deploying it on kubernetes and testing app resilience > with chaoskube which randomly kills some pods from time to time. > It turned out that one component of the app leaves h2 file corrupted: > > [ERROR] 2020-03-10T16:08:15,009Z [main] > pool.HikariPool.throwPoolInitializationException > - HikariPool-1 - Exception during pool initialization. > org.h2.jdbc.JdbcSQLException: File corrupted while reading record: null. > Possible solution: use the recovery tool [90030-197] > at org.h2.message.DbException.getJdbcSQLException(DbException.java:357) > ~[myjar.jar:?] > at org.h2.message.DbException.get(DbException.java:168) ~[myjar.jar:?] > > > Is there any option or parameter which should be used to prevent the > corruption ? Any hint how to cope with it ? >
-- 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/44c430d9-847f-4454-84f6-7c105020b881%40googlegroups.com.
