Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
A merkle tree file may be corrupted during write or by some other error. This should only be a temporary problem since the scanner will rewrite it on its next run. Until that happens failures should be handled accordingly:
- Clients calling the readMerkleTree API should be able to cleanly fail on a corrupted file. The server does not deserialize it before sending.
- Reconciliation should regenerate a local checksum file if it is corrupted, as if it does not exist.
- File write can be done by renaming a temp file into place to avoid corruption from partial writes. The file would either be present or absent if a write fails, but not partially written.
- Tests using corrupted files should be added.
Attachments
Issue Links
- links to