[OAK-3305] Self recovering instance may not see all changes

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0, 1.2, 1.3.4
• Fix Version/s: 1.0.32, 1.2.17, 1.3.6, 1.4
• Component/s: core, mongomk
• Labels: resilience
• Epic Link: DocumentMK resilience
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 27/Aug/15 11:08
• Updated: 04/Jul/16 13:54
• Resolved: 02/Sep/15 06:34

Description

When a DocumentNodeStore instance is killed and restarted, the _lastRev recovery mechanism is triggered on startup. It may happen that the restarted instance does not see all changes that were recovered.

Issue Links

• depends upon: OAK-3079 LastRevRecoveryAgent can update _lastRev of children but not the root

Sub-Tasks

• Create a copy of MemoryDocumentStore: Closed