33 | Occasionally slow requests in load testing" resize="256mb" page="2kb" /> <recovery enabled="true" sync="false" path="." max="128mb ... values for recovery => max (try smaller first). Larger processing => cache value. More RAM on the machine. Using a dedicated disk only for the odb file and another dedicated disk only for the recovery |
22 | Replication error on slave restartI'm trying to enable replication on master server that was running with "recovery" enabled ... you shut down the master server normally and then you should not have a recovery file (ended ... " /> </general> <database> <size initial="256kb" resize="256kb" page="2kb" /> <recovery |
17 | Setting temp directory location in ObjectDB an ObjectDB version, but it seems that you are using an old ObjectDB 1.x version because the recovery file ... only for ObjectDB 2.x anyway. In ObjectDB 1.x the recovery file path is calculated using: String dirPath = System.getProperty("com.objectdb.recovery.path"); if (dirPath == null) { dirPath |
15 | Database Transaction Replayer is useful for two different purposes: It enables recovery from a database failure by replaying |
15 | Database Replication and ClusteringObjectDB supports master-slave replication (cluster). When replication (or clustering) is used, the same database is managed on multiple machines (nodes), possibly in different geographic locations. This could help in achieving high availability, fault tolerance and prompt disaster recovery. In |
15 | Database FilesHi. According the docs, "Every transaction commit is first written to the recovery file and then to the database". During my testing, every time I make a transaction the recovery file keeps growing ... is written to the recovery file it can be considered as part of the database. When the recovery file |
7 | cannot delete objects after crash (see issue 2283) completes please post its output. Exploring the cause of the recovery failure is still in progress ... report of such a failure after recovery. Probably you do not have a copy of the database and the recovery file (odb$) after shutdown and before the server was restarted, but if you do have it may help |
4 | Unexpected error when loading all entity instance database termination followed by opening the database with no recovery (e.g. if the database file was moved or copied to another location without the recovery file). support Support Hello, thats ... . However, if recovery is enabled then the database should be repaired automatically |
3 | EOFException should be used). Deleting an ObjectDB database recovery file or recording directory if it exists, or copying, moving or transferring an ObjectDB database file without its recovery file or recording directory. Power failure when the database is being updated - if recovery file is disabled. Using |
2 | [ODB1] Chapter 5 - JDO Connections, which is called auto recovery, is not supported by the free edition of ObjectDB. To ensure database consistency, it is recommended that write caching be disabled - at least for the database file and the recovery |
