Reindexer failed to prepare required rollback

[jriker1]

Latest head as of a day or so ago, get the following errors in the logs.  Set to reindex but after done and restart again still gives the same errors.

13:25:02,859  INFO  [management.subsystems.ChildApplicationContextFactory] Startup of 'thirdparty' subsystem, ID: [thirdparty, default] complete
13:25:08,417  ERROR [index.AbstractReindexComponent.threads] Reindexer     3 failed with error: 00190001 Failed to prepare: requires rollback.
13:25:08,481  ERROR [index.AbstractReindexComponent.threads] Reindexer     5 failed with error: 00190003 Failed to prepare: requires rollback.
13:25:11,465  ERROR [index.AbstractReindexComponent.threads] Reindexer     6 failed with error: 00190009 Failed to prepare: requires rollback.
13:25:11,482  ERROR [index.AbstractReindexComponent.threads] Reindexer     7 failed with error: 00190007 Failed to prepare: requires rollback.
13:25:13,946  ERROR [index.AbstractReindexComponent.threads] Reindexer     9 failed with error: 00190005 Failed to prepare: requires rollback.
13:25:14,200  INFO  [node.index.FullIndexRecoveryComponent]     10 % complete.
13:25:26,359  INFO  [node.index.FullIndexRecoveryComponent]     20 % complete.
13:25:41,360  INFO  [node.index.FullIndexRecoveryComponent]     30 % complete.
13:25:54,390  INFO  [node.index.FullIndexRecoveryComponent]     40 % complete.
13:26:06,422  INFO  [node.index.FullIndexRecoveryComponent]     50 % complete.
13:26:19,084  INFO  [node.index.FullIndexRecoveryComponent]     60 % complete.
13:26:32,918  INFO  [node.index.FullIndexRecoveryComponent]     70 % complete.
13:26:44,798  INFO  [node.index.FullIndexRecoveryComponent]     80 % complete.
13:27:13,348  INFO  [node.index.FullIndexRecoveryComponent]     90 % complete.
13:27:30,424  INFO  [node.index.FullIndexRecoveryComponent]     100 % complete.
13:27:32,057  INFO  [node.index.FullIndexRecoveryComponent] Index recovery completed.


Any ideas?

Thanks.

JR

[cvillemure]

Doing the forced reindex worked with Alfresco 3.3g

However, since we were not ready to upgrade to 3.3g yet, i've written a webscript that parse my structure node by node and try to search the nodes with lucene.  If lucene do not find the node, I then know there's a index corruption.  When i find that kind of node, i add a tag to that node and the remove it, which force lucene to reindex this node.

Parsing my entire tree with the above scripts, also resolved my index problem.

[kevinr]

Hi,

I think this was posted in the wrong forum which is why you haven't had much of a response! Share Developers aren't going to be much use with a repo indexer issue  :shock:

From what I can see, it looks like this issue should be resolved by upgrading to 3.3, delete the indexes and perform FULL reindex.

Thanks,

Kev

[fracat71]

Hi,
i know that is not the rigth place of the thread but i have a similar problem.
The situation is a clusterd environment with a node down for 1 moth so i think a full reindex is needed.

17:46:38,968  ERROR [index.AbstractReindexComponent.threads] Reindexer    12 failed with error: 00030009 Failed to prepare: requires rollback.
17:46:39,122  ERROR [index.AbstractReindexComponent.threads] Reindexer    13 failed with error: 00030005 Failed to prepare: requires rollback.
17:46:39,186  ERROR [index.AbstractReindexComponent.threads] Reindexer    14 failed with error: 00030003 Failed to prepare: requires rollback.
17:46:39,263  ERROR [index.AbstractReindexComponent.threads] Reindexer    15 failed with error: 00030007 Failed to prepare: requires rollback.
18:13:22,357  INFO  [node.index.FullIndexRecoveryComponent]    10 % complete.
18:43:59,711  INFO  [node.index.FullIndexRecoveryComponent]    20 % complete.
19:14:26,183  INFO  [node.index.FullIndexRecoveryComponent]    30 % complete.
19:43:27,238  INFO  [node.index.FullIndexRecoveryComponent]    40 % complete.
20:14:08,026  INFO  [node.index.FullIndexRecoveryComponent]    50 % complete.
20:43:13,312  INFO  [node.index.FullIndexRecoveryComponent]    60 % complete.
21:10:57,492  INFO  [node.index.FullIndexRecoveryComponent]    70 % complete.
21:39:40,309  INFO  [node.index.FullIndexRecoveryComponent]    80 % complete.
22:08:08,288  INFO  [node.index.FullIndexRecoveryComponent]    90 % complete.
22:41:14,791  INFO  [node.index.FullIndexRecoveryComponent]    100 % complete.
22:41:51,916  INFO  [node.index.FullIndexRecoveryComponent] Index recovery completed.‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍