I have an Examine index that is critical to the website's core functionality. Most of the time the index works perfectly with no issues.
However every now and then, the Index will go from 6000 documents to 0, and I have to log in to the back office, click re-build index and then everything will work again.
Can any one speculate/explain why this might be happening, I have never seen this problem happen on my local machine, so maybe its something to do with the server set up...?
It is a custom index, the data that drives the index are in a custom database. Since the last time it magicly failed. It hasn't happened again... but it will randomly sometimes just stop working... hmm
We had this problem again yesterday, rebuild the index everything working again. - By going through that documentation I noticed that we don't have WEBSITEDISABLEOVERLAPPED_RECYCLING setting in our configuration file.
Could this be the cause of our problem? What exactly does this setting do?
Examine Index needs rebuilding randomly - Why?
I have an Examine index that is critical to the website's core functionality. Most of the time the index works perfectly with no issues.
However every now and then, the Index will go from 6000 documents to 0, and I have to log in to the back office, click re-build index and then everything will work again.
Can any one speculate/explain why this might be happening, I have never seen this problem happen on my local machine, so maybe its something to do with the server set up...?
Any ideas?
Is it custom Index or built in Index? Do you have custom data gathering code?
It is a custom index, the data that drives the index are in a custom database. Since the last time it magicly failed. It hasn't happened again... but it will randomly sometimes just stop working... hmm
What is the server setup? Is it on azure?
Yes.. its running on Azure. Never been able to recreate the issue locally...
Can you double check and ensure the examine config is using the correct providers https://our.umbraco.com/Documentation/Getting-Started/Setup/Server-Setup/azure-web-apps thats if you are using webapps
We had this problem again yesterday, rebuild the index everything working again. - By going through that documentation I noticed that we don't have WEBSITEDISABLEOVERLAPPED_RECYCLING setting in our configuration file.
Could this be the cause of our problem? What exactly does this setting do?
is working on a reply...