[OAK-7703] Format version handling on upgrade

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: documentmk
• Assignee: Unassigned
• Reporter: Marcel Reutegger
• Created: 09/Aug/18 07:27
• Updated: 09/Aug/18 07:28

Description

The current upgrade procedure for a DocumentNodeStore deployment requires downtime and reduced capacity for some time. Future upgrade should work without downtime. This means a format version change introduced with OAK-4529 must be handled differently. It must be possible to update the DocumentNodeStore to a version that supports a newer format version, but writing in that version must be postponed to a later point, when all cluster nodes have been upgraded.

Issue Links

• relates to: OAK-4529 DocumentNodeStore does not have a repository software version range check