[OAK-1822] NodeDocument _modified may go back in time

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0
• Fix Version/s: 1.0.1, 1.1.0
• Component/s: core, mongomk
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 15/May/14 09:08
• Updated: 01/Oct/14 13:14
• Resolved: 11/Jun/14 12:01

Description

In a cluster with multiple DocumentMK instances the _modified field of a NodeDocument may go back in time. This will result in incorrect diff calculations when the DocumentNodeStore uses the _modified field to find changed nodes for a given revision range.

Issue Links

• is related to: OAK-1840 Failure when setting up DocumentNS fixture