topic SOLR Tracking Failed in Alfresco Archive

SOLR Tracking Failed

mangar — Tue, 26 Jun 2012 17:12:13 GMT

I have upgraded my Alfresco to 4.0.d comm from 3.3 Everything went fairly well, except for the SOLR stuff. I had to copy the original /solr directory from my initial install to my backed up alf_data, but that's it. Everything seems to work fine except for my log files filling up with this:Jun 26,

Re: SOLR Tracking Failed

andy — Wed, 27 Jun 2012 08:44:52 GMT

Hi

Do not copy the SOLR index from anywhere (as it does not apply to the same DB)
Start with a clean SOLR set up - do not take the SOLR index data from a clean install for example)
SOLR checks the first transaction information in the index against the DB to guard against mis-configuration.
It will not add information from repository A to an index based on repository B ….

Also see ALF-14237

There is an issue with ACL change set timestamps when upgrading to 4.0 which you will have to fix by hand (until there is another community release)

update alf_acl_change_set c
set c.commit_time_ms = ((select min(t.commit_time_ms) from alf_transaction t) + c.id)
where c.commit_time_ms < (select min(t.commit_time_ms) from alf_transaction t)

There are some issue that can stop SOLR tracking (eg errors in JSON for odd user names)
If you see a 500 error and SOLR tracking stops use the FIX action as described on the SOLR wiki page.

(These issues are fixed in the enterprise product.)

Andy

Re: SOLR Tracking Failed

dbachem — Tue, 03 Jul 2012 10:05:44 GMT

Dear Andy, I have the same problem (Initial transaction not found with correct timestamp) but didn't understand if your ACL patch gives a solution. According to your comment…

> Do not copy the SOLR index from anywhere (as it does not apply to the same DB)
> Start with a clean SOLR set up - do not take the SOLR index data from a clean install for example)
> SOLR checks the first transaction information in the index against the DB to guard against mis-configuration.
> It will not add information from repository A to an index based on repository B ….

Do you have any further instructions how to "start with a clean SOLR set up"?

My usage scenario is following: in our production environment we migrated from 3.4 to 4.0.c some month ago, but for some reason our service partner disabled SOLR completely. Now i want to install a "staging" copy of this production system, dumped postgres and copied alf_data. The target system is a clean alfresco_community_4.0.d with default configuration, meaning SOLR enabled. So my intent is to get this staging system running with production data but WITH solr. What is the right way to do this?

Re: SOLR Tracking Failed

andy — Tue, 03 Jul 2012 18:50:21 GMT

Hi

Do not use the index from the install - make sure there is no SOLR index.
The SOLR logging should report creating the index.

Yes you will require the patch/fix.

Andy