U4-2920 - InternalIndexSet becomes corrupted and cannot rebuild

Created by Tim Payne 24 Sep 2013, 08:56:44 Updated by Shannon Deminick 21 Jun 2017, 07:58:15

We've had an issue on two sites recently, one running 6.1.3 and one running 4.11.8, where the InternalIndexSet has become corrupted and cannot be rebuilt. The Index folder just contains two files of around 1KB each, and if you view the indexes in Luke, they are either empty, or only have one or two malformed documents (e.g. important fields like nodeId are missing).

This causes a couple of issues. One is that the media library intermittently fails, as it tries the cache, and dies, because fields are missing, so never hits the fallback, or because the items don't seem to end up in the fallback media library call either (not sure if that method uses the same index set or not). The second issue is that publishing in the back office breaks when publishing new Documents, with an error "Value cannot be null. Parameter name: attribute" as part of the re-index that gets called when the page is published.

The other indexes are fine, and all seem happy. If we try and rebuild the InternalIndexSet using the Examine dashboard, then it usually dies. But if we delete the InternalIndex Lucene indexes and rebuild, then it's fine, and everything works again.

We're still working on trying to reliably replicate the issue, if we manage to do so, I will update here.

Comments

Shannon Deminick 21 Jun 2017, 07:58:15

Closing issue due to inactivity - see blog post for details https://umbraco.com/blog/issue-tracker-cleanup/


Priority: Normal

Type: Bug

State: Closed

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 4.11.8, 6.1.3

Due in version:

Sprint:

Story Points:

Cycle: