Lucene Index Recovery
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2008 12:20 PM
I am in the final stages of testing with HSQL for proof of concept. Things were going well until today. I am receiving an error in a single workspace and believe it's attributed to corrupt indices.
A system error happened during the operation: Non-root node has no primary parent: child: workspace://SpacesStore/89c4306d-5f3e-11dd-a4fc-45ab39a2b329
I have been sifting through the forum and have only seen reference to index recovery mode. Since I am a relative newbie, I am unfamiliar with where the mode needs to be set. I altered the index-recovery-context file only to receive SEVERE errors when reloading. A single workspace is affected, all others are intact.
Would anyone have a more concise description of the recovery procedure?
A system error happened during the operation: Non-root node has no primary parent: child: workspace://SpacesStore/89c4306d-5f3e-11dd-a4fc-45ab39a2b329
I have been sifting through the forum and have only seen reference to index recovery mode. Since I am a relative newbie, I am unfamiliar with where the mode needs to be set. I altered the index-recovery-context file only to receive SEVERE errors when reloading. A single workspace is affected, all others are intact.
Would anyone have a more concise description of the recovery procedure?
Labels:
- Labels:
-
Archive
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2008 03:40 PM
Well, I did figure out how to reindex and my initial assumption was wrong. I noticed that I'm missing the discussion space that was associated with the content space. That is the non-root node that is orphaned. Does anyone have feedback on how I can recreate the association? I can still see the discussions from an upper nesting, but not from the space. I have also lost all the content within the parent space. Hope fully that wil return with the discussion space
