Issue : After Publishing content through back office its not getting visible on all instances. If i refresh page its shows and another page refresh content updates are vanishing. Seems published content is not availble acorss all instances. Anyone faced this issue.
When you scale out in Azure like this, you are essentially 'load balancing' 5 instances with a single database table.
When you publish something in the backoffice, it updates the Umbraco Cache on the instance you have published on, but the other instances are unaware of the change...
which we certainly used on some big Azure web app hosted sites, to do a similar job to what 'flexible load balancing' does today on the later versions...
... it wasn't ever super perfect, but worked on the same principal of putting update instructions into a database table, and allowing the other instances to see those instructions and update their cache when things had been published.
Content Synching not happening on multiple instances after publish
Umbraco Version v6.2.5
Application hosted in Microsoft Azure
Recently Scaled-out to 5 instances in the Azure.
Issue : After Publishing content through back office its not getting visible on all instances. If i refresh page its shows and another page refresh content updates are vanishing. Seems published content is not availble acorss all instances. Anyone faced this issue.
Hi Rahul
When you scale out in Azure like this, you are essentially 'load balancing' 5 instances with a single database table.
When you publish something in the backoffice, it updates the Umbraco Cache on the instance you have published on, but the other instances are unaware of the change...
... Going back in time to this version of Umbraco ... flexible load balancing: https://our.umbraco.com/Documentation/Getting-Started/Setup/Server-Setup/Load-Balancing/flexible-v7 hadn't been introduced yet to the 'core'
The only form of load balancing required you to configure the names of each server in your umbracosettings.config, and then when a publish occurred, a web request would ping each server and tell it to rebuild it's cache - see https://our.umbraco.com/Documentation/Getting-Started/Setup/Server-Setup/Load-Balancing/traditional
With your scaling out in Azure, though you'd never necessarily know what those server names would be, what with it all being magic in the cloud...
... anyway also back in the day there was this plugin:
https://github.com/darrenferguson/cloud-umbraco-cache-refresh
which we certainly used on some big Azure web app hosted sites, to do a similar job to what 'flexible load balancing' does today on the later versions...
... it wasn't ever super perfect, but worked on the same principal of putting update instructions into a database table, and allowing the other instances to see those instructions and update their cache when things had been published.
regards
Marc
is working on a reply...