[OAK-7869] Commit queue stuck when input stream of blob blocks

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0, 1.2, 1.4, 1.6.0, 1.8.0
• Fix Version/s: 1.10.0, 1.9.13
• Component/s: documentmk
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 31/Oct/18 09:13
• Updated: 14/Dec/18 11:30
• Resolved: 29/Nov/18 09:28

Description

This is the same scenario as described in OAK-7867 but for the DocumentNodeStore.

The behaviour of the DocumentNodeStore is slightly different. The rogue InputStream will block the CommitQueue inside the DocumentNodeStore and prevent other commits from finishing. Other commits may proceed up to the point where changes are persisted, including the final update on the commit root document, but the merge calls for those commits will never return.

It doesn't look like the issue can cause data loss, but can still affect availability of the system as other writes are blocked. Writes on other cluster nodes may also be affected because a blocked CommitQueue means already persisted commits are not propagated through the background update thread. Commits on other cluster nodes then may conflict because changes from the affected cluster node are not yet made visible.

Issue Links

• relates to: OAK-7867 Flush thread gets stuck when input stream of binaries block