Task #3865
MNDeployment #2564: ORNL DAAC
Clear and re-harvest Daac Content
100%
Description
While browsing the ornl daac MN and comparing to CN content during investigation of ORNL Daac object counts, I noticed that the content on the MN appears to have changed/been modified in place. As this is out of bounds of CN synchronization - which assumes immutable content - these changes are not present on the CN. For example:
https://cn-orc-1.dataone.org/cn/v1/meta/scimeta_846.xml vs http://mercury-ops2.ornl.gov/ornldaac/mn/v1/meta/scimeta_846.xml
https://cn-orc-1.dataone.org/cn/v1/meta/scimeta_66.xml vs http://mercury-ops2.ornl.gov/ornldaac/mn/v1/meta/scimeta_66.xml
the size, checksum, upload dates are different.
It may be necessary to delete the ORNL Daac content from the CN to allow re-harvesting of the current content.
Assigning to Chris for approval or rejection of this task. I believe we can use the script Robert developed to clear this content if approved.
ornldaac-invalid-replicas.csv 
(78.4 KB)
History
#1 Updated by Chris Jones almost 11 years ago
- File ornldaac-invalid-replicas.csv added
- Status changed from New to In Progress
- File ornldaac-invalid-replicas.csv added
After auditing the checksums on the CN compared to those on the DAAC MN, there are 978 invalid replicas on the MN (in that they are using the same identifier for a different byte stream). I'm attaching the list here as a CSV file.
#2 Updated by Chris Jones over 10 years ago
- Status changed from In Progress to Closed
- translation missing: en.field_remaining_hours set to 0.0
Robert performed this. Closing.
