[jira] [Commented] (OAK-3104) Version garbage collector doesn't collect a rolled back document if it was never deleted

["Vikas Saurabh (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627665#comment-14627665 ] 

Vikas Saurabh commented on OAK-3104:
------------------------------------

As discussed with [~mreutegg], we should probably set_deletedOnce flag while rolling back. I'd add a test and patch later.

> Version garbage collector doesn't collect a rolled back document if it was never deleted
> ----------------------------------------------------------------------------------------
>
>                 Key: OAK-3104
>                 URL: https://issues.apache.org/jira/browse/OAK-3104
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: mongomk
>            Reporter: Vikas Saurabh
>            Priority: Minor
>
> If a commit gets rolled back it can leave (in case the document was never deleted explicitly) a document in a state like:
> {noformat}
> {
>        "_id" : "7:/etc/workflow/packages/2014/10/12/rep:ours",
>        "_deleted" : {
>        },
>        "_commitRoot" : {
>        },
>        "jcr:primaryType" : {
>        },
>        "_modified" : NumberLong(1413126245),
>        "_children" : true,
>        "_modCount" : NumberLong(2)
> }
> {noformat}
> If the path is fairly busy, the document can get created naturally later and then follow the usual cycle. But, at times, such documents are ephemeral in nature and never re-used. In those cases, such documents can remain silently without getting collected.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)