[
https://issues.apache.org/jira/browse/OAK-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-4668:
---------------------------------
Labels: candidate_oak_1_2 (was: candidate_oak_1_2 candidate_oak_1_4)
Merged
* 1.4 - 1796269
> Make async index more resilient on documentmk
> ---------------------------------------------
>
> Key: OAK-4668
> URL: https://issues.apache.org/jira/browse/OAK-4668
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
> Reporter: Alex Parvulescu
> Assignee: Alex Parvulescu
> Labels: candidate_oak_1_2
> Fix For: 1.5.9, 1.6.0
>
> Attachments: OAK-4668.patch, OAK-4668-v2.patch, OAK-4668-v3.patch
>
>
> The async index update suffers in an eventual consistency store from stale
> reads of the root node. It may happen that in a cluster an indexing job
> running concurrently on more nodes, would not see the lease updates coming
> from another cluster node, so it would end up wiping away checkpoints and/or
> triggering a full reindex.
> There is not much we can do at this level, but make the code a bit more
> resilient for this specific case (_reindex due to missing reference
> checkpoint_) by issuing a write+read operation to force a root revision
> update which would hopefully prevent a full reindex.
> For background, the preferred solution is to have an upper layer choose the
> node where the async jobs run (aka. use sling discovery bundles).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
