When does umbraco decides to rebuild the cache and the examine indexes
Hi
We have a rather big site. The site is deployed using scripts (octopus deploy). Every time there is a new version, the scripts create a new folder and copy a the newest (clean) version in. This means that all the indexes need to be rebuild from scratch. This process takes about 5 minutes after the first hit of the website, which is a PITA. After the reindexing is done, the site is working fine.
We tried to recover the files (index files, plugin cache) from the previous deploy but this won't stop examine (umbraco?) from reindexing the complete site.
Does anyone know when (or how) umbraco/examine/lucene decides that the indexes are out of date and all content should be reindexed?
Or does anyone know how to trick the site into reusing the old (and up-to-date) indexes?
When does umbraco decides to rebuild the cache and the examine indexes
Hi
We have a rather big site. The site is deployed using scripts (octopus deploy). Every time there is a new version, the scripts create a new folder and copy a the newest (clean) version in. This means that all the indexes need to be rebuild from scratch. This process takes about 5 minutes after the first hit of the website, which is a PITA. After the reindexing is done, the site is working fine.
We tried to recover the files (index files, plugin cache) from the previous deploy but this won't stop examine (umbraco?) from reindexing the complete site.
Does anyone know when (or how) umbraco/examine/lucene decides that the indexes are out of date and all content should be reindexed? Or does anyone know how to trick the site into reusing the old (and up-to-date) indexes?
Kind regards Damiaan
is working on a reply...