[MGNLTOOLS-35] Broken nodes finder Created: 19/Jun/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Repository Tools
Component/s: None
Affects Version/s: 1.0.4
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Matteo Pelucco Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
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)
Date of First Response:

 Description   

Sometimes Jackrabbit lose control on child nodes and the result is the SearchIndexer exception "missing node....".
The only way to fix it is to try to remove the parent node, but it is a time consuming action.
For large data storage, more than one node can be missing and doing a manual fix means to have a lot of downtime exposure.

Idea: create a script that will found all broken nodes and manage them, maybe removing the parent.



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 10:40:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.