...
NOTE: Depending on the size of your repository, the type of database, and/or the capacity of your database server, the rebuild can take anywhere from a few seconds to several hours (i.e if you have many millions of objects).
Continuing a failed rebuild
If a previous rebuild of the Fedora indices was interrupted and you have some records indexed in the database you can "continue" the rebuild with the following flag:
| Code Block |
|---|
-Dfcrepo.rebuild.continue=true |
This flag will restart the process of iterating over all objects in the OCFL filesystem but will only index objects it does not find in the existing indices. This flag takes precedence over the fcrepo.rebuild.on.start flag, if both are specified the indices will NOT be truncated.
| Info |
|---|
For the full list of database properties, please refer to the Database section of the Properties documentation. You can find additional information on this wiki about configuring supported databases and the structure of the tables in the database. |
Additional Configuration
To help with long rebuilds, optional properties can be passed in
| Property | Default Value | Note |
|---|---|---|
| -Dfcrepo.rebuild.validation | true | Enables validation of the ocfl repository before running reindexing. Set to false to skip this step. |
| -Dfcrepo.rebuild.validation.fixity | false | Sets a flag in the ocfl validation to run fixity checks on bitstreams during validation. Set to true to enable fixity checks. Note: -Dfcrepo.rebuild.validation must also be enabled for fixity checking |
| -Dfcrepo.ocfl.verify.inventory | true | Tells the ocfl repository that the inventory for an ocfl object should be validating during read and write operations. Set to false to disable checking of the inventory. |