[
https://issues.apache.org/jira/browse/OAK-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved OAK-1784.
-----------------------------------
Resolution: Fixed
Merged into 1.0 branch in revision http://svn.apache.org/r1591384
> Async index update persists conflict markers
> --------------------------------------------
>
> Key: OAK-1784
> URL: https://issues.apache.org/jira/browse/OAK-1784
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, mongomk
> Affects Versions: 0.20
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Critical
> Fix For: 1.0
>
>
> A long running test I performed yesterday failed with a FileNotFoundException
> in the lucene index. After analyzing the issue it turned out the async index
> update persisted a conflict markers introduced by a rebase call. So far I'm
> not able to reproduce it with a more simple test setup and after a shorter
> time (the initial test failed after 10 hours). Given the way the async index
> update work, there shouldn't be any conflicts, because it's the only
> component writing into this location of the repository.
> As an immediate workaround, I'd like to add the AnnotatingConflictHandler &
> ConflictValidator combo to the merge call to make sure a commit with conflict
> markers does not get persisted.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
