Major Description
BlobIdTracker can resurrect deleted blob ids from a previous run when running in a clustered setup by also synchronizing blob references from other cluster/shared nodes which don't have information about the deleted blob ids.
The effect of this is that when blob gc is executed again it identifies those ids as candidates and logs a warning when trying to delete them since they had already been deleted in the last gc execution.
The locally tracked files at each of the instances should be purged after synchronizing with the datastore.