I have a umbraco site setup in Azure for load balancing. It has been working fine
But we have encountered a issue where it hasn't published updates out to all the site instances. So depending on what instance, you are on you might see the updated content.
I don't know if it is related or not, but we also recently upgraded to 7.2.8 (was 7.2.1) and getting the following 2 errors come through
System.Web.HttpException: A public action method 'Index' was not found
on controller 'Umbraco.Web.WebServices.ScheduledPublishController'.
Generated: Wed, 02 Sep 2015 05:27:16 GMT
And this one
System.Web.HttpException: The file '/umbraco/ping.aspx' does not
exist.
the config for distributed calls will be in your /config/umbracoSettings.config
(what are your settings for this ?)
After each publish from your backoffice instance, webservice calls are made to each server listed in distributedCall, to tell it to update it's content from the the Umbraco Database.
So this can fail if the config is not correct, or if the servers cannot resolve each other's server address to be able to make the refresh call to:
/umbraco/webservices/cacherefresher.asmx
With 'Web Apps' new server instances could be spun up by Azure at any moment and their configuration would not be in your distributedCalls serverlist, making it difficult to load balance Umbraco with Azure Web Apps.
The good news is Umbraco 7.3.0 will introduce a new database based method for distributed calls, so servers can be agnostic of each other and rely on a shared database queue for details of refresh instructions.
Not Publishing to all Load Balancing Site
I have a umbraco site setup in Azure for load balancing. It has been working fine
But we have encountered a issue where it hasn't published updates out to all the site instances. So depending on what instance, you are on you might see the updated content.
I don't know if it is related or not, but we also recently upgraded to 7.2.8 (was 7.2.1) and getting the following 2 errors come through
And this one
Hi Nadia
Are these Azure VMs or 'Web Apps' (formerly known as Websites) ?
Traditional Umbraco load balancing, requires setting up of Distributed Calls
https://our.umbraco.org/documentation/getting-started/setup/server-setup/load-balancing
the config for distributed calls will be in your /config/umbracoSettings.config
(what are your settings for this ?)
After each publish from your backoffice instance, webservice calls are made to each server listed in distributedCall, to tell it to update it's content from the the Umbraco Database.
So this can fail if the config is not correct, or if the servers cannot resolve each other's server address to be able to make the refresh call to:
/umbraco/webservices/cacherefresher.asmx
With 'Web Apps' new server instances could be spun up by Azure at any moment and their configuration would not be in your distributedCalls serverlist, making it difficult to load balance Umbraco with Azure Web Apps.
The good news is Umbraco 7.3.0 will introduce a new database based method for distributed calls, so servers can be agnostic of each other and rely on a shared database queue for details of refresh instructions.
Shannon talked about this here at codegarden:
https://vimeo.com/channels/939955/132815038
Thanks, yes I am using WebApps.
So when its scaled up, can't garantee that published changes get deployed out.
is working on a reply...