So we recently had examine issues with umbraco on azure. So we updated our config so that we can sync and auto build on app pool restart. We think recently azure moved as around as we can see an entry in umbracoserver table for today. Not long after this the site gave
Server Error in '/' Application. Runtime Error Description: An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception. The request has been terminated.
Then it sorted it self out. In the umbraco log we get:
2016-05-17 14:13:02,713 [9] ERROR UmbracoExamine.LocalStorage.LocalTempStorageIndexer - Could not create index writer with snapshot policy for copying, the index cannot be used
2016-05-17 14:13:06,538 [9] ERROR Umbraco.Core.CoreBootManager - An error occurred running OnApplicationStarted for handler Umbraco.Web.BatchedDatabaseServerMessengerStartup
Lucene.Net.Store.LockObtainFailedException: Lock obtain timed out: NativeFSLock@D:\home\site\wwwroot\AppData\TEMP\ExamineIndexes\Internal\Index\write.lock: System.IO.IOException: The process cannot access the file 'D:\home\site\wwwroot\AppData\TEMP\ExamineIndexes\Internal\Index\write.lock' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
Could this error be becuase the index is still rebuilding?
We initially had auto rebuild set to false but then that was giving us empty indexes and parts of site failing. Now after azure move we get indexes but because they are big and they are also synching we get error 500 page while things are rebuilding.
Its definitely happening on the switch because you see an entry in the db table. There was another post where someone was watching for this entry in the db table then they were rebuilding not sure how they were doing it though I did ask the question but no reply.
Please could you give some more information how did you manage to amend Examine issues when Azure moves app between Web Workers ?
I can see that when new Web worker is copying app from old web worker, there is an issue with copying examine indexes as far as they are in use and have write.lock -> as I understand because of that the App must to rebuild indexes -> what causes our production site to be down
My conf :
Umbraco version : 7.5.4
Examine version : 0.1.70
On Azure i have web app which is not load balanced
Examine issue on azure
So we recently had examine issues with umbraco on azure. So we updated our config so that we can sync and auto build on app pool restart. We think recently azure moved as around as we can see an entry in umbracoserver table for today. Not long after this the site gave
Then it sorted it self out. In the umbraco log we get:
Could this error be becuase the index is still rebuilding?
Regards
Ismial
We got exactly the same error. I have no idea ... yet. So just lurking in and hoping for a magic unicorn.
Damiaan,
We initially had auto rebuild set to false but then that was giving us empty indexes and parts of site failing. Now after azure move we get indexes but because they are big and they are also synching we get error 500 page while things are rebuilding.
Its definitely happening on the switch because you see an entry in the db table. There was another post where someone was watching for this entry in the db table then they were rebuilding not sure how they were doing it though I did ask the question but no reply.
Regards
Ismail
Damiaan,
Some further investigation on this https://our.umbraco.org/forum/extending-umbraco-and-using-the-api/77496-media-in-external-index
Regards
Ismail
We are having very similar problems with large index's in Azure too, has anyone found a concrete solution to this yet?
Ayo,
Did you check out https://our.umbraco.org/Documentation/Getting-Started/Setup/Server-Setup/Load-Balancing/flexible until the azure provider is released (its currently still in development) you need follow guidance here.
We have it working on a big site and fixed our issue
@Ismail
Please could you give some more information how did you manage to amend Examine issues when Azure moves app between Web Workers ?
I can see that when new Web worker is copying app from old web worker, there is an issue with copying examine indexes as far as they are in use and have write.lock -> as I understand because of that the App must to rebuild indexes -> what causes our production site to be down
My conf :
Umbraco version : 7.5.4
Examine version : 0.1.70
On Azure i have web app which is not load balanced
According to the link https://our.umbraco.org/Documentation/Getting-Started/Setup/Server-Setup/Load-Balancing/flexible i have Sync flag for as described in "PreExamine v0.1.80" and AzureLocalStorageDirectory set for all indexers and serachers in ExamineSettings.config.
Also machine key is removed from ExamineIndex.config
Is there any way to avoid Lucene issues(causing app restart/ rebuild) when azure moves to the new Web Worker ?
Mati,
We just followed the guidelines and so we have index in app data and temp storage.
Ensure it follows above. There is expermental azure lucene blob storage but its not production ready yet.
We have this settings already :(
But I will check everything once again .
Thanks Ismail :)
is working on a reply...