[
https://issues.apache.org/jira/browse/OAK-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14719975#comment-14719975
]
Michael Marth commented on OAK-3314:
------------------------------------
If Trash is either a different DS implementation or a separate part in the same
DS impl: this issue could be probably be looked at as a use case for OAK-3140
> DataStore / BlobStore garbage collection: move to trash instead of delete
> -------------------------------------------------------------------------
>
> Key: OAK-3314
> URL: https://issues.apache.org/jira/browse/OAK-3314
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: blob
> Reporter: Thomas Mueller
>
> Bugs in datastore garbage collection are quite severe, because if binaries
> that are still needed are deleted, then recovering from the problem is
> problematic and slow: restoring a backup is needed, if there is a backup.
> To speed up and simplify recovering from a missing binary, instead of
> deleting files directly, they could be moved to "trash" (directory, or marked
> as trash). When trying to access such an entry, the data store / blob store
> could fail (as it does now), so that manual intervention is needed. Or it
> could recover automatically, but log an exception.
> "Trash" could also be moved to a slower disk, compressed, stored in
> generations (trash_1, trash_2,...).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
