[
https://issues.apache.org/jira/browse/OAK-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Jain updated OAK-3872:
---------------------------
Attachment: OAK_3872.patch
A simple test and a possible fix is attached. All tests pass with the fix.
[[email protected]] Can you please review the patch.
The above is a strong possibility during the concurrent run of blob gc and
async index update as there is a likelihood that an older lucene blob gets
recreated which is marked for GC. Since, it would have been updated it should
not be deleted.
> [RDB] Updated blob still deleted even if deletion interval lower
> ----------------------------------------------------------------
>
> Key: OAK-3872
> URL: https://issues.apache.org/jira/browse/OAK-3872
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: blob, rdbmk
> Reporter: Amit Jain
> Attachments: OAK_3872.patch
>
>
> If an existing blob is uploaded again, the timestamp of the existing entry is
> updated in the meta table. Subsequently if a call to delete
> (RDBBlobStore#countDeleteBlobs) is made with {{maxLastModifiedTime}}
> parameter of less than the updated time above, the entry in the meta table is
> not touched but the data table entry is wiped out.
> Refer
> https://github.com/apache/jackrabbit-oak/blob/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/document/rdb/RDBBlobStore.java#L510
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
