[OAK-4573] S3 fetching record leads to multiple calls and background download

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.2.18, 1.4.6, 1.5.6, 1.6.0
• Component/s: blob
• Assignee: Amit Jain
• Reporter: Amit Jain
• Created: 19/Jul/16 03:12
• Updated: 10/Nov/16 09:50
• Resolved: 19/Jul/16 04:00

Description

While deleting a blob during GC, a DataRecord is fetched to check that the modified timestamp is older than configured and deleted only of its older.
For S3 this leads to a call to #getRecord() which tries to proactively download corresponding binaries and makes multiple calls to get lastModified timestamp and the length.

This leads to similar behavior as observed in OAK-4430 but in the delete flow.

Issue Links

• is related to: OAK-4577 BlobGC performance improvements
• relates to: OAK-4430 DataStoreBlobStore#getAllChunkIds fetches DataRecord when not needed