Our web site is running on Umbraco 7.12.3, in Azure. We are following https://our.umbraco.com/documentation/Getting-Started/Setup/Server-Setup/load-balancing/flexible setup and have one Web App for master instance, and one Web App for front instances with scale-out to 3 instances.
Sometimes, we face a situation when one of front instances stop receiving content updates from master/DB. We can see that newly published page not appeared on issues instance, or content updates not reflected on it. Future content updates in backoffice gives no results on instance with such issue. The only way we know to solve issue - is force cold boot on issued instance.
We are getting know about problem when editors mention about it. As other instances works as expected issue could be invisible for a some period of time. So we don't have exact scenario to reproduce it or log message with error.
Have anybody faced with such cases earlier?
Content synchronization stop working
Hi all,
Our web site is running on Umbraco 7.12.3, in Azure. We are following https://our.umbraco.com/documentation/Getting-Started/Setup/Server-Setup/load-balancing/flexible setup and have one Web App for master instance, and one Web App for front instances with scale-out to 3 instances. Sometimes, we face a situation when one of front instances stop receiving content updates from master/DB. We can see that newly published page not appeared on issues instance, or content updates not reflected on it. Future content updates in backoffice gives no results on instance with such issue. The only way we know to solve issue - is force cold boot on issued instance. We are getting know about problem when editors mention about it. As other instances works as expected issue could be invisible for a some period of time. So we don't have exact scenario to reproduce it or log message with error. Have anybody faced with such cases earlier?
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.