topic Re: Progress on rebuilding indexes in Alfresco Archive

Progress on rebuilding indexes

rcm01 — Sat, 30 Jul 2011 23:23:23 GMT

Using Community 3.4d. I have a corrupted instance and need to rebuild the lucene indexes. I found a post that suggested checking the file alfresco.log for the status of the rebuild. I can't find a file called alfresco.log. Any suggestions where I can check the progress?

Re: Progress on rebuilding indexes

rcm01 — Sun, 31 Jul 2011 03:15:26 GMT

I found what I think is the right log, Alfresco\tomcat\logs\stdout_20110730.log

Here's the last two entries and this doesn't look good to me……does anyone have any ideas about this?

22:07:33,558 INFO [node.index.FullIndexRecoveryComponent] Index recovery started: 1,403,281 transactions.
Exception in thread "Thread-14" java.lang.OutOfMemoryError: Java heap space

We are doing an evaluation of this product and so far its less than stellar. Any help would be appreciated.

Re: Progress on rebuilding indexes

andy — Mon, 01 Aug 2011 19:03:23 GMT

Hi

How much heap does it have?
Is there a full stack trace?
Have you any particularly large transactions or lareg documents that are being converted in memory.

There are a few options/potential issues depending on the cause here.
There are several options that you would normally tweak for larger repositories.

You would be better evaluating an enterprise trial.

Andy

Re: Progress on rebuilding indexes

gacarrilloc — Sat, 25 Aug 2012 23:21:20 GMT

Hi,

It also happened to me and it was because I left the default configuration of memory of the JVM (i.e. 64 M), and did multiples import tasks of large zip files. To recover the service, I started modifyng the JAVA_OPTS variable in the ./tomcat/bin/catalina.sh file (e.g. add the line JAVA_OPTS="$JAVA_OPTS -Xmx512m" at the beginning of the file) <however i don't know if it was really necessary to started up alfresco again>, and then i set ./tomcat/temp/catalina.pid to the process id that was assigned to alfresco before it crashed.

Then I could stop Alfresco, and start it again without problems, but now I have to check if the indexes are ok.