[OAK-2077] Improve the resilence of the OrderedIndex for dangling links

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.0.9, 1.1.3
• Assignee: Davide Giannella
• Reporter: Davide Giannella
• Created: 05/Sep/14 15:11
• Updated: 07/Apr/15 20:24
• Resolved: 28/Nov/14 16:04

Description

It could happens that along the various lanes of the SkipList
implemented by the OrderedIndex we encounter dangling links to nodes
that has been previously removed.

While it's not clear yet how to reproduce it on the prune() side
we could improve the seek() and maybe fetchKeyNode() method
for considering the use case and optionally clean-up after it.

Issue Links

• is related to: OAK-2305 Merge OAK-2202 into the 1.0 branch
• relates to: OAK-2285 Builder does not exist error during async index update
• requires: OAK-2202 OrderedIndex should not return the whole index on property=$value statement