Description
When at-most archive expiration was introduced in 2016-09, it introduced a defect in the operation that deletes-for-space. When no expiration is configured (as will be the case for all existing customers), the delete-for-space will be incorrectly skipped because nothing will be expired (obviously), and the archive target will be stuck at full. They will then cease to archive anything new.
<br>
Version Introduced
Affects versions 7.9.33 through 8.1.6, and RCs 8.0.0/8.0.1
<br>
Platform
All
<br>
Steps to reproduce
- Configure archiving (free run will accelerate condition). Do not configure expiration.
- Allow archive target to fill.
- Once full, recorder will routinely attempt to delete oldest content on target to make space for archiving newer content.
<br>
Expected result
Successful deletion of oldest, continued archiving of newest, no archive task errors.
<br>
Actual result
No longer delete oldest content, no archiving of newest, task repeatedly fails with PURGE_FAILED and never proceeds, repeated log message pair:
9/12/2016 12:07:29 PM ArchivePI Warning Archiving error – ran out of target space
9/12/2016 12:09:27 PM ArchivePI Warning Archiving task error status PURGE_FAILED
<br>
Work Around
Configure expiration slightly less than the day capacity of your target, and expiration will actually provide analogous behavior.
Upgrade to fixed version 8.0.2.
<br>
Version Fixed
8.0.2
<br>
Keywords
at-most, archive, expiration, archivePI