You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2016/11/10 09:51:00 UTC

[jira] [Updated] (OAK-4573) S3 fetching record leads to multiple calls and background download

     [ https://issues.apache.org/jira/browse/OAK-4573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke updated OAK-4573:
--------------------------------
    Fix Version/s: 1.6

> S3 fetching record leads to multiple calls and background download
> ------------------------------------------------------------------
>
>                 Key: OAK-4573
>                 URL: https://issues.apache.org/jira/browse/OAK-4573
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: blob
>            Reporter: Amit Jain
>            Assignee: Amit Jain
>             Fix For: 1.6, 1.5.6, 1.4.6, 1.2.18
>
>
> While deleting a blob during GC, a DataRecord is fetched to check that the modified timestamp is older than configured and deleted only of its older.
> For S3 this leads to a call to #getRecord() which tries to proactively download corresponding binaries and makes multiple calls to get lastModified timestamp and the length.
> This leads to similar behavior as observed in OAK-4430 but in the delete flow.



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