What are the consequenses of deleting the lucene index?

[msim...@gmail.com]

Afternoon all.

As part of our new deployment process (which currently in progress), we sometimes need to copy the postgres database from one server to another. Unsurprisingly, HippoCMS throws lots of indexing related errors on startup, and it doesn't serve content properly.

When I delete the lucene index storage folder, and restart the webapp, it runs fine.

What are the consequences of deleting this index? I will need to do this in production as well.

If it's a problem, are there any ways I can make the index consistent with the new data without deleting the storage folder? I've tried setting the SearchIndex autoRepair, enableConsistencyCheck and forceConsistencyCheck parameters in repository.xml to true, but it didn't fix the issues.

Thanks for your help.
Mark.

[William Borg Barthet]

Hi Mark,

as far as I know if you delete the index, it will be recreated on startup. So the only real consequence of deleting it is that you have to wait for it to be created. If you have a lot of data in your repo, this could take a considerable amount of time (30 mins and more), but you should be fine once it is done.

William

--
Hippo Community Group: The place for all discussions and announcements about Hippo CMS (and HST, repository etc. etc.)
 
To post to this group, send email to hippo-c...@googlegroups.com
RSS: https://groups.google.com/group/hippo-community/feed/rss_v2_0_msgs.xml?num=50
---
You received this message because you are subscribed to the Google Groups "Hippo Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hippo-communi...@googlegroups.com.
Visit this group at http://groups.google.com/group/hippo-community.
For more options, visit https://groups.google.com/d/optout.

--

Amsterdam - Oosteinde 11, 1017 WT Amsterdam
Boston - 745 Atlantic Avenue, Boston, MA 02111
 
US +1 877 414 4776 (toll free)
Europe +31(0)20 522 4466
www.onehippo.com