We are in the process of migrating a Version 7.15.3 site to Version 8.6.1; I have set up a Master and a Replica server and this is working as expected (so if content is updated on the back office server the front end content is also updated). We are running on Azure web apps.
However, I've noticed in the logs that any time any body publishes a document there are 3 lots of the following message from
"App is shutting down so index batch operation is ignored" with the source context Umbraco.Examine.UmbracoContentIndex
I assume this means that the indexes are not being written to, but it's a bit odd that examine seems to think that the App is shutting down - has anybody else experienced this on 8.6.1?
I have this and I am not running on Azure. I am however working against a restored database from production that is running in a load-balanced environment so am now stripping out inactive servers in the umbracoServer table in case that is related.
"App is shutting down so index batch operation is ignored" Whenever a document is published on Master Server
Hello Umbracians!
We are in the process of migrating a Version 7.15.3 site to Version 8.6.1; I have set up a Master and a Replica server and this is working as expected (so if content is updated on the back office server the front end content is also updated). We are running on Azure web apps.
However, I've noticed in the logs that any time any body publishes a document there are 3 lots of the following message from
"App is shutting down so index batch operation is ignored" with the source context Umbraco.Examine.UmbracoContentIndex
I assume this means that the indexes are not being written to, but it's a bit odd that examine seems to think that the App is shutting down - has anybody else experienced this on 8.6.1?
Examine is configured as per the article here:
https://our.umbraco.com/documentation/getting-started/setup/server-setup/azure-web-apps
And I have explicitly set the umbracoApplicationURL and implemented custom IServerRegistrars as per the docs here:
https://our.umbraco.com/documentation/getting-started/setup/server-setup/Load-Balancing/flexible-advanced#explicit-master-scheduling-server
Does anybody have any ideas?!
Thanks in advance,
Chris
If anybody else is experiencing this, it appears to be related to running on Azure - see GitHub issue:
https://github.com/umbraco/Umbraco-CMS/issues/8006
I have this and I am not running on Azure. I am however working against a restored database from production that is running in a load-balanced environment so am now stripping out inactive servers in the
umbracoServertable in case that is related.I have the settings it suggests and we still get this often..
Logs here are also often flooded with this after publishing an item.
All Azure-related settings appear correct. And the app is definitely not shutting down ...
Are you on 8.6.1 or 8.6.2+? Do you have multiple servers?
For us on 8.6.1 we had to:
1) Set SqlMainDomLock on the back office server only
2) Set up server with explicit master/scheduling roles (as per the docs here https://our.umbraco.com/documentation/getting-started/setup/server-setup/Load-Balancing/flexible-advanced#explicit-master-scheduling-server)
3) Set the Azure setting regarding disabling overlapping recycling to 1 (must be set in Azure, cannot be set in web.config)
4) Add the IgnoreLocalDb flag setting to true in code via a composer
Since upgrading to 8.6.2 we had to:
1) Set SqlMainDomLock on all servers
2) Remove the Azure setting regarding overlapping recycling
3) Set IgnoreLocalDb to false (in fact I just commented out the code)
4) Keep explicit roles for master/replica servers
Sorry, I was too brief, and thanks for re-iterating.
Will see if it's temporary/unrelated or holds steady for now.
Thanks for the tip regarding 8.6.2.
is working on a reply...