Bug #7955
Synchronization should check dateSysMetaModified when adding tasks to processing queue
Start date:
2016-12-21
Due date:
% Done:
100%
Milestone:
None
Product Version:
*
Story Points:
Sprint:
Description
When retrieving PIDs to synchronize using listObjects against a Member Node, the dateSysMetaModified should be checked to be sure that the entry is newer than the earliest time requested in the listObjects call.
This is a protective measure to ensure that the CN does not continually try and synchronize old content for a MN that is misbehaving and not responding correctly to a timeslice request on listObjects.
Related issues
Associated revisions
fixes #7955. Added check that the modification date of the objectInfo is within the harvest window.
fixes #7955. Added check that the modification date of the objectInfo is within the harvest window.
History
#1 Updated by Dave Vieglais about 8 years ago
- Related to Story #7716: How to facilitate resubmission of sync Failures? added
#2 Updated by Rob Nahf almost 8 years ago
added check against harvestStartDate before adding to the queue. (in 2.3 branch)
#3 Updated by Rob Nahf almost 8 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100