[
https://issues.apache.org/jira/browse/JCR-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15958891#comment-15958891
]
Csaba Varga commented on JCR-4126:
----------------------------------
Also, if it's not too much to ask, can we get this fix backported to the
Jackrabbit version used by the Oak 1.2.x branch? We are currently using AEM
6.1, so we can only uptake fixes made to the 1.2.x branch.
> Shared FileDataStore throws exception if two processes try to add the same
> file concurrently
> --------------------------------------------------------------------------------------------
>
> Key: JCR-4126
> URL: https://issues.apache.org/jira/browse/JCR-4126
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-data
> Affects Versions: 2.15.1
> Reporter: Csaba Varga
> Priority: Minor
> Attachments: concurrent-datastore-fix.diff
>
>
> The FileDataStore implementation can throw an IOException if multiple
> repositories share the same data store and multiple repositories try to add
> the same record at the same time. This can happen easily when you set up
> multiple AEM publisher instances to share the same data store to save disk
> space. (AEM uses Oak, but the Oak file blobstore implementation ends up using
> the Jackrabbit FileDataStore implementation, so at the end of the day the bug
> affects the latest Oak and latest AEM as well.)
> We have noticed this issue via log analysis. When we publish the same asset
> to all of our publisher instances, we are seeing a recurring IOException in
> the log. The author instance eventually retries the publish operation and by
> that time, there is no race condition and the operation succeeds, but the
> situation is still not ideal.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
