topic Lucene error with batch loads in Alfresco Archive

Lucene error with batch loads

okto — Mon, 12 Nov 2007 08:19:53 GMT

Hi!I'm development an application using Alfresco (at the moment we are using alfresco-community-tomcat-2.1.0.zip but in the future will use the enterprise version) with the Lucene jar version 2.1.0.I'd developed a java interface using your's apis and works quite fine but when I'd started with the te

Re: Lucene error with batch loads

andy — Tue, 13 Nov 2007 11:10:12 GMT

Hi

No one else has hit this issue. Can you point us to the lucene bug.

We try to keep up to date with lucene and would intend to move to 2.2 next time. If there are issues with 2.1 then we are more likely to move (or use a patched version of the 2.1 code)

Andy

Re: Lucene error with batch loads

okto — Tue, 13 Nov 2007 11:47:12 GMT

Hi again,

I'd been searching for the web withy the bug in Lucene but I don't find it…
Nevertheless if you want traces of error with Lucene I had a lot of them. I had made an insert test that crash if I don't make sleeps during the execution of it.

It's necessary to pause the inserts in Alfresco to let lucene index all the contents? Maybe I need to configure something in the config files.

Thanks a lot for your time

PS: i'll keep on searching for the web with the lucene bug.

Re: Lucene error with batch loads

tonytony — Fri, 21 Mar 2008 13:27:16 GMT

Any resolution to this? I get this error rebuilding indexes. Im trying it right now with more stack to see if that fixes the problem.

Re: Lucene error with batch loads

tonytony — Fri, 21 Mar 2008 17:46:00 GMT

setting tomcat with -Xss1m allowed me to rebuild indexes.

Re: Lucene error with batch loads

andy — Tue, 15 Jul 2008 10:26:34 GMT

Hi

This stack trace shows you have too many parts to your index.

The index merger has failed for some reason.
You can turn debug on to see why.

There are fixes to make index merging more resilient - but not in the community version you are using.

I suggest you get an enterprise trial.

If your tweak to teh JVM settings fail you will have to rebuild the index.

Andy

Re: Lucene error with batch loads

msporled — Thu, 17 Jul 2008 14:15:42 GMT

You could also try finding lucene settings that were more resilient for your load type.

lucene.query.maxClauses
lucene.indexer.batchSize
lucene.indexer.minMergeDocs
lucene.indexer.mergeFactor
lucene.indexer.maxMergeDocs
lucene.indexer.maxFieldLength