Project: duracloud
Issue DURACLOUD-663: Secondary Provider Audit Entry Sequencing
This issue is to resolve the bug occasionally seen in the content manifest when running dup-on-change. Sometimes ingest and delete messaging events lose sequence on the secondary provider. To create this scenario, an item must already exist in a space, then be deleted and immediately re-ingested. It is not a common production scenario. The attached audit log demonstrates such a case. Note, the actual content in both the primary and secondary stores were actually the same, but the secondary store does not show file-6.txt in its manifest: space-id content-id MD5 manitest file-0.txt b1946ac92492d2347c6235b4d2611184 manitest file-10.txt b1946ac92492d2347c6235b4d2611184 manitest file-1.txt b1946ac92492d2347c6235b4d2611184 manitest file-2.txt b1946ac92492d2347c6235b4d2611184 manitest file-3.txt b1946ac92492d2347c6235b4d2611184 manitest file-4.txt b1946ac92492d2347c6235b4d2611184 manitest file-5.txt b1946ac92492d2347c6235b4d2611184 manitest file-6.txt b1946ac92492d2347c6235b4d2611184 manitest file-9.txt b1946ac92492d2347c6235b4d2611184
Story points: 2