Re: Indexation and cache problems

At 19:38 10.01.2006, Nicolas Belisle wrote:
>It is text information in new pages and modified pages.

We would need more details about such an error in order to help you...

>>>- The re-indexing takes more than 20 hours !
>>
>>Why not simply upgrading to Jahia 4.1? There 
>>was a major refactoring of the re-indexation 
>>utility in there which now run as a back-end task + a few optimization...
>
>I will look into it.
>
>Internally, we use Lucene for a document 
>management system and indexing around 20 000 
>pages of text (coming from a database and the filesystem) takes minutes...

This is not Lucene which takes time but the 
loading of all the jahia content objects, 
metadata, etc, etc.. which are also indexed. 
Moreover we do not only index everything as free 
text in lucene but also indexed fields from a 
structured manner... so this takes a bit more time...

>This not an option. We just bought the server for Jahia :)
>Is it normal for a production environment to 
>need so much cache, for less than 2000 pages ?

No. You should have a cache whic is not limited 
in size and which "eat" all the heap? Are you 
connected to a LDAP server? Are you sure your 
groups.ldap.preload in groups.ldap.properties is at false?

Else sorry but this is difficult to help you with 
the level of information we have. Memory usage 
and/or out of memory in java can come from a lot 
of different things from a memory leak (are you 
sure your JSP compiler (Jasper) is in production 
or fork mode as it is known to have some memory 
leaks?) to templates scriplters which are badly 
coded to portlets which are preloaded (but not used), etc, etc...

So this is really difficult to help you just with 
the level of information we currently have and 
without some kind of more detailled 
investigation. One thing you may do is to make a 
small script which log into the Admin Center of 
Jahia and save automatically every hour the page 
which summarizes the status of all the caches. 
Then we may perhaps better see (if this is a 
Jahia cache issue) which is the guilty cache you should perhpas limit....

Regards,
Stéphane