Description
On a new setup if the blob gc is executed before taking a snapshot then the blobs ids are retrieved from the datastore and GC removes are synchronized with this retrieved file. But these removed blob ids may also be present in the tracker generation and therefore may get resurrected on next snapshot. This will happen as no snapshot has taken place which is possible if the blobGcMaxAgeInSecs is configured to be less than the blobTrackSnapshotIntervalInSecs.
The effect of the above situation would be that the removed blob ids would always turn up as GC candidates until the tracker is reset and log a warning during GC as they are not present anymore.
Attachments
Issue Links
- relates to
-
OAK-4200
[BlobGC] Improve collection times of blobs available
-
- Closed
-