[OAK-3388] Inconsistent read in cluster with clock differences

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0, 1.2
• Fix Version/s: 1.0.22, 1.2.7, 1.3.8, 1.4
• Component/s: core, mongomk
• Labels: resilience
• Epic Link: DocumentMK resilience
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 10/Sep/15 12:39
• Updated: 02/Mar/16 14:29
• Resolved: 29/Sep/15 14:57

Description

This issue is similar to OAK-2929 but related to how the DocumentNodeStore reads a node state when there is a clock difference between multiple cluster nodes. The node state read from a NodeDocument may not be correct when there is a clock difference.

Issue Links

• is related to: OAK-3411 Inconsistent read on DocumentNodeStore startup