Currently we are running a Umbraco 7.3-beta3 in azure.
We have the following setup :
1 VM that is used for content editing
1 Web app at the moment for front end (umbraco backend access is restrictred using IIS rewrites)
When I publish something in the content editing instance (VM) these changes are not always visible on the front end (Web app)
When I look in the umbracoServer table I see both instances as active. Also the last notified date get's updated after changes for both instances.
But when I log in through FTP on the web app I see that the file in /App_Data/TEMP/DistCache/ doesn't have the latest id found in the umbracoCacheInstruction table
When the web app restarts this get's updated all content changes are visible.
Am I missing some config settings or code to make this work?
It seems to work flawless on our dev environments. When one developer publishes something on his machine, all other registered instances are updated.
I just discoverd that the lastNotifiedDate doesn't get update when doing a publish for the web app. This only happens after the app has been restarted.
I did some more testing. Only seems to occur when a node doesn't have a domain assigned. But only in the Azure environment. If i publish a node that has a domain assigned all changes are visible after that.
Loadbalancing issues in 7.3-beta3
Hi
Currently we are running a Umbraco 7.3-beta3 in azure.
We have the following setup :
When I publish something in the content editing instance (VM) these changes are not always visible on the front end (Web app)
When I look in the umbracoServer table I see both instances as active. Also the last notified date get's updated after changes for both instances.
But when I log in through FTP on the web app I see that the file in /App_Data/TEMP/DistCache/ doesn't have the latest id found in the umbracoCacheInstruction table
When the web app restarts this get's updated all content changes are visible.
Am I missing some config settings or code to make this work?
It seems to work flawless on our dev environments. When one developer publishes something on his machine, all other registered instances are updated.
Dave
I just discoverd that the lastNotifiedDate doesn't get update when doing a publish for the web app. This only happens after the app has been restarted.
Dave
I did some more testing. Only seems to occur when a node doesn't have a domain assigned. But only in the Azure environment. If i publish a node that has a domain assigned all changes are visible after that.
Still digging :-)
Dave
After some more digging I discoverd that the syncing is done when you make a request to the load balanced instance.
But we have some custom Url providers and virtual node handlers in place and it doesn't seem to sync when you call a virtual url.
Dave
So did some more digging.
It seems when you do a request to the website the Sync method on the Umbraco.Core.Sync.DatabaseServerMessenger is called.
However when we call a page with a virtual node this method doesn't seem to be called.
From logs when calling a normal page
From the logs for a request to a virtual node :
Dave
Just created a issue for this on the tracker : http://issues.umbraco.org/issue/U4-7056
Just updated the issue with the following information.
The issue has been marked as solved on the issue tracker. So I will mark this post as a solution as well
is working on a reply...