[OAK-9358] DocumentNodeStore may accumulate split candidates

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.38.0
• Fix Version/s: 1.40.0, 1.22.7
• Component/s: documentmk
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 16/Feb/21 13:44
• Updated: 13/Apr/21 09:08
• Resolved: 17/Feb/21 10:53

Description

This is a regression introduced by OAK-9149. The split candidates in DocumentNodeStore may contain document IDs that actually don't need to be split. Commit#checkSplitCandidate() does a very quick check based on the size of the document and then leaves it to the background update to perform more thorough check and perform the split if necessary. As of OAK-9149, an ID for a document that does not need to be split in the background update is not removed from the split candidates and the background update checks it in every cycle. It is also possible that distinct split candidates accumulate over time and slow down the background operation significantly.

Issue Links

• is caused by: OAK-9149 Use batch calls in backgroundSplit
• links to: GitHub Pull Request #276