topic Solr tracking stopped working in Alfresco Archive

Solr tracking stopped working

aussen2 — Mon, 14 May 2012 16:43:15 GMT

We set up a fresh installation of Alfresco Community 4.0.d about three months ago and everything was working fine until recently. Then out of the sudden the following error messages started to appear in our log files about a week ago. We can still find some documents via search but not all. If we de

Re: Solr tracking stopped working

andy — Tue, 15 May 2012 09:07:06 GMT

Hi

See the Alfrecsoi and SOLR wiki page.

Use the CHECK and FIX URLs.

Please report any errors logged on the Alfresco side.
There wil be a real cause.

Andy

Re: Solr tracking stopped working

aussen2 — Tue, 15 May 2012 10:45:01 GMT

Here is the output from /solr/admin/cores?action=CHECK:


<?xml version="1.0" encoding="UTF-8"?>
<response>
<lst name="responseHeader"><int name="status">0</int><int name="QTime">0</int></lst>
</response>
‍‍‍‍‍‍

And the one from /solr/admin/cores?action=FIX:


<?xml version="1.0" encoding="UTF-8"?>
<response>
<lst name="responseHeader"><int name="status">0</int><int name="QTime">32753</int></lst>
</response>
‍‍‍‍‍‍

Nothing special showed up in the log files when calling theses URLs.

Re: Solr tracking stopped working

aussen2 — Tue, 15 May 2012 11:00:48 GMT

When calling /solr/admin/cores?action=SUMMARY&wt=xml we get the following output indicating that the last commit for the workspace store was 3+ days ago while the archive store seems to work just fine.


<?xml version="1.0" encoding="UTF-8"?>
<response>
<lst name="responseHeader"><int name="status">0</int><int name="QTime">0</int></lst><lst name="Summary"><lst name="alfresco"><long name="Last Index Commit Time">1336744804210</long><date name="Last Index Commit Date">2012-05-11T14:00:04.21Z</date><str name="Lag">270165 s</str><str name="Duration">P0Y3DT3H2M45.211S</str><bool name="Active">false</bool><long name="Timestamp for last TX on server">1337014969421</long><date name="Date for last TX on server">2012-05-14T17:02:49.421Z</date></lst><lst name="archive"><long name="Last Index Commit Time">1337014969421</long><date name="Last Index Commit Date">2012-05-14T17:02:49.421Z</date><str name="Lag">0 s</str><str name="Duration">-P0Y</str><bool name="Active">false</bool><long name="Timestamp for last TX on server">1337014969421</long><date name="Date for last TX on server">2012-05-14T17:02:49.421Z</date></lst></lst>
</response>
‍‍‍‍‍‍

Could the cause for the tracking error be a corrupted node in the repository? Another search related process started to throw InvalidNodeRefExceptions recently (see https://forums.alfresco.com/en/viewtopic.php?f=52&t=41135#p130275 for details). How would the Solr tracking react if it came along such a node? Would it go on to index all the other nodes or would it just stop indexing?