cancel
Showing results for 
Search instead for 
Did you mean: 

Solr4 : Asynchronous indexing not working

mat34
Champ on-the-rise
Champ on-the-rise

Hello everyone!

I upgraded my alfresco community edition (5.0 to 5.2) respecting specific Alfresco documentation:

   - Install the new version (from Alfresco installer)

   - Copy old content store in new installation directory (10Gb)

   - Switching config in properties to use old Postgre database  

   - Regenerate SSL keys...

Firstly, the startup of Alfresco is OK (no errors) but It need many hours to be fully available (100% CPU during at least 4 hours without errors ). I thought it was only for first start (building index for first time) but it take this time for every restart of Alfresco. I don't know if this time is a normal value but is complicated for testing properties and restart application.

After the startup, Alfresco Share interface is OK with all functionnality. My problem occur when I add or modify a file, the file is well added in the interface but it seem not indexed, is never added in "recently updated/modified" category , recents and searching actions (rss functions..).

If I check Solr admin console, i notice that lastModified value is never updated and there are no log in catalina.out or solr.log) ...

Solr

core info

UpdateHandler details : 

In SolrR logging console , I found some errors after startup at ~16:00

errors

details

For "Java heap space" message I already increase JAVA_OPTS values in setenv.sh like this

Any ideas? 

Thanks a lot

1 ACCEPTED ANSWER

cesarista
World-Class Innovator
World-Class Innovator

Yes, that seems the problem. Default Heap settings -Xms and -Xmx from ctl.sh are probably taking preference over the ones from setenv.sh, and so, the java out of memory problems.

So just delete -Xmx and -Xms settings from ctl.sh and restart Alfresco. I prefer to use setenv.sh instead of ctl.sh

Regards.

--C.

View answer in original post

10 REPLIES 10

afaust
Legendary Innovator
Legendary Innovator

You apparently have an error on the Repository side (logs not provided), which is indicated by SOLR receiving a 500 response code for its calls to the APIs to retrieve index-relevant changes. Check the alfresco.log file for any issues, correct them, and try again.

If you included the SOLR log file as an attachement (along with alfresco.log) instead of a short excerpt screenshot, people on this platform could potentially help you out more effectively.

mat34
Champ on-the-rise
Champ on-the-rise

You'r right,I uploaded log files to my question!

Thanks again

cesarista
World-Class Innovator
World-Class Innovator

My two cents:

- You can check SOLR indexation tracking via SOLR page in OOTB Support Tools.

- You can also try to get more information setting DEBUG in log4j for SOLR tracking:

log4j.logger.org.alfresco.solr.tracker.CoreTracker=DEBUG

Regards.

--C.

mat34
Champ on-the-rise
Champ on-the-rise

Hello, thanks,

I'm not in my office this week!

I will make sure that I reply when I get back!

Happy holidays