[MAGNOLIA-6658] Handle versions suffering from InconsistentVersioningState exceptions Created: 09/May/16  Updated: 17/May/16  Resolved: 13/May/16

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 5.4.6
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Ilgun Ilgun Assignee: Ilgun Ilgun
Resolution: Obsolete Votes: 0
Labels: backup, version, versioning
Remaining Estimate: 0d
Time Spent: 2d 2m
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLBACKUP-100 Test stability of RepositoryCopier im... Closed
is depended upon by MGNLBACKUP-99 Refactor backup module to use Reposit... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Sprint: Basel 43
Story Points: 5

 Description   

With the version of 2.0, backup module is using RepositoryCopier API MGNLBACKUP-99. While testing the new implementation MGNLBACKUP-100, we encountered an issue with versioning.

The issue is that, if one tries to version a node while the backup is ongoing. There is a possibility of having the version node in InconsistentState.
After some further observation, it is clear that one may encounter the situation only if the node to be versioned had not been versioned before. In other words, versioning the first version of a given node is causing the exceptions while the backup is ongoing.

Proposed Solution

It is possible to handle those situation by simple stripping the version node. Jackrabbit may have some mechanism to handle those but it also fails because simply the version history is missing and therefore that's the cause of the exceptions at the first place.



 Comments   
Comment by Ilgun Ilgun [ 13/May/16 ]

Its been clear that, there is no perfect solution for this issue. Therefore we will be closing this ticket as obsolete and tackle the main problem in an different level.

Generated at Mon Feb 12 04:16:36 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.