...
- These python scripts - fcrepo-testing - can be used to load RDF content and binary content to a Fedora repository and verify the integrity of the loaded resources. Output from the load process can be used to verify the integrity of a 'restored' repository. See the README for more info.
- This script can be used to walk your repository, failing if a non-success response is encountered.
| Tested by | Platform | Container (Tomcat/Jetty) | Database Backend | From Fedora | To Fedora Version | Number of RDF Resources | Number of Binaries | Size of Backup (du -h .) | Success? | Notes |
|---|---|---|---|---|---|---|---|---|---|---|
| Linux | Tomcat (7.0.72) | Postgres (9.4) | 4.6.1 | 4.7.1-RC1 | 461,568 | 1,671 | 48G |  | ||
| Mac | Jetty (Standalone) | 4.7.1-RC1 | 25,600 | 0 | | |||||
| Mac | Jetty (Standalone) | 4.7.1-RC1 | 4.7.1-RC1 | 12,800 | 12,800 | 13GB | |
NB: "Success" is measured not by receiving a "204 No Content" message after the 'fcr:restore' command, but by performing a GET on every resource in the repository and receiving "200 OK" messages.
Multi-thread Tests
These tests are designed to ensure the integrity of the repository when loading content in a multi-threaded fashion. Testing for repository corruption should entail confirming the successful load of resources, the successful fetching of resources, and the successful deletion of resources. Prior to 4.6.1, these tests would result in repository corruption.
Resources
- These python scripts - fcrepo-testing - can be used to load RDF content and binary content to a Fedora repository and verify the integrity of the loaded resources. See the README for more info.
| Tested by | Platform | Container (Tomcat/Jetty) | Database Backend | Number of Threads | Number of RDF Resources | Number of Binaries | Success? RC-1 | Notes |
|---|---|---|---|---|---|---|---|---|
| Mac | Jetty (Standalone) | 2 | 12,800 | 12,799 | | Tried to load 12,800 binary resources, but 1 binary resource resulted in a 4xx error during load. This was a failed ingest so in the end the successful 201s matched the 200s during verification. | ||
| Mac | Jetty (Standalone) | 8 | 12,800 | 12,706 | | Tried to load 12,800 binary resources, but 94 binary resources resulted in 500 errors during load. These were failed ingests so in the end the successful 201s matched the 200s during verification. | ||
| Mac | Jetty (Standalone) | 8 | 25,600 | 0 | |
NB: "Success" is measured by receiving all 200s when performing a GET on each loaded resource, and all 204s when finally deleting the content.
Vagrant Tests
| Code Block |
|---|
vagrant destroy vagrant up |
...