I'm not sure if the "Umbraco.Core.MainDom.Lock" should be set on both web apps, or just the admin, or maybe the frontend but not the slot (or mayby just the slot?)
Instructions for the earlier versions made it clear to only do this on the Admin web app, but it's not mentioned for the 8.6.4+ instructions...
The confusion that makes it hard to explain, is that when the setting was introduced in 8.6.0 there was an issue with replica servers and scaling out in Azure, but it still really provided stability for the backoffice server that isn't scaled out.
This was resolved in 8.6.4 and now replica and backoffice servers can have their domain locking controlled via the database.
The other 'workarounds' in the documentation still 'work around' the issue, eg disabling overlapping recycling and ignoring the local db on a replica servers - but with the new MainDom setting in place you shouldn't need to use the workarounds for either server.
Azure setup unclear about the use of MainDom.Lock
Hi,
Hoping someone can help clarify the documentation regarding a scalable Azure setup.
My environment is:
Trying to follow the documentation here: https://our.umbraco.com/Documentation/Getting-Started/Setup/Server-Setup/Load-Balancing/azure-web-apps#v864
I'm not sure if the "Umbraco.Core.MainDom.Lock" should be set on both web apps, or just the admin, or maybe the frontend but not the slot (or mayby just the slot?)
Instructions for the earlier versions made it clear to only do this on the Admin web app, but it's not mentioned for the 8.6.4+ instructions...
Thanks!
Hi Ismael
Apply the setting to both.
The confusion that makes it hard to explain, is that when the setting was introduced in 8.6.0 there was an issue with replica servers and scaling out in Azure, but it still really provided stability for the backoffice server that isn't scaled out.
This was resolved in 8.6.4 and now replica and backoffice servers can have their domain locking controlled via the database.
https://our.umbraco.com/download/releases/compare?from=8.6.3&to=8.6.4
The other 'workarounds' in the documentation still 'work around' the issue, eg disabling overlapping recycling and ignoring the local db on a replica servers - but with the new MainDom setting in place you shouldn't need to use the workarounds for either server.
regards
Marc
Awesome, thanks lot Marc!
is working on a reply...