Page 1 of 1
Re-indexing repository
PostPosted:Mon Mar 27, 2017 2:52 pm
by openkm_user
Hi,
We have around 2 million documents in our repo.
We want to re-index the whole repository.
Does the community edition offer parallel mode for the hibernate.indexer.mass.indexer.
Thanks!
Re: Re-indexing repository
PostPosted:Tue Mar 28, 2017 6:31 pm
by jllort
Take a look here
https://docs.openkm.com/kcenter/view/ok ... eters.html ( take in mind documentation talks about version 6.3.3 what is available from here
https://github.com/openkm/document-management-system ( we have still not released the official installer, actually only we have released the application what must be upgrade manually as is described here
https://docs.openkm.com/kcenter/view/ok ... guide.html )
Can you describe your hardware, number of core and disk type ?
Re: Re-indexing repository
PostPosted:Wed Mar 29, 2017 7:08 pm
by openkm_user
We have 6.3.2 currently running and have a configuration property hibernate.indexer.mass.indexer, will this work in parallel mode if enabled?
Re: Re-indexing repository
PostPosted:Thu Mar 30, 2017 8:13 pm
by jllort
Should try with 6.3.3, because there're a lot of changes between version 6.3.2 and 6.3.3 ( this is a major release with a lot of improvements )
Re: Re-indexing repository
PostPosted:Sat Apr 01, 2017 4:24 pm
by openkm_user
Thank you, we moved to 6.3.3 and made configuration changes to our need. After starting re-indexing it ran for few hours and front-end showed
"session timeout" error but
RebuildIndexesServlet_20170401.log file kept updating and final lines are,
Code: Select all2017-04-01 05:09:59,170 INFO NodeBase progress 1,935%%
2017-04-01 05:09:59,170 INFO NodeBase progress 1,935%%
2017-04-01 05:10:53,699 INFO END - Rebuild Lucene indexe
Does this mean re-index completed successfully?
Re: Re-indexing repository
PostPosted:Sat Apr 01, 2017 4:46 pm
by jllort
Yes, the log indicates the repository index has finished ( another indicator is that repository removes the read only set ).
About session timeout, sometimes happens, what URL are you using for accessing OpenKM ?