7 | getting "Unexpected total page count" error when diagnosis mu db by ObjectDB doctor. (abnormally) during a writing action, and recovery is not applied. However, it doesn't mean necessarily |
7 | Date field Index is corrupted due to time change close without its associated recovery file. However, it is also possible (although extremely rare |
7 | Optimistic lock failed" /> <recovery enabled="false" sync="false" path="." max="100mb" /> <recording enabled |
7 | ObjectDB version 2.2 has been released after index deletion. Changed default configuration (enabled recovery, disabled recording). Fixed a critical |
7 | significant performance decrease" /> </general> <database> <size initial="256kb" resize="256kb" page="2kb" /> <recovery enabled |
1 | ObjectDB 2.2.0 and reusing space after index deletion. Changed default configuration (enabled recovery, disabled |
1 | NullPointerException using with "refresh" method Please check the recovery setting in your ObjectDB configuration. If it set to sync="false" (default |
1 | Errors after unexpected server shutdown with the data or corrupted. This shouldn't happen of course as recovery from failure should protect data |
1 | each 1-2 days objects on some objectdb level lock/block each other="2kb" /> <recovery enabled="true" sync="false" path="." max="96mb" /> <recording |
1 | several times a day queries take several minutes files on query execution. <recovery ... max="128mb" /> Consider decreasing the maximum size to force |
