load balanced server - do all files go on the share ?
We're experiencing extreme (30-90seconds) delays when publishing new pages and modifications on our server farm, on a labserver with the same website it takes a split second.
Is it possible that there are conflicts somewhere when there are multiple iis servers are using the same set of files (we have the entire website in a shared folder) that cause the save times to go up to about a minute instead of a split second?
The documentation talks about possible issues with lock files when using multiple url's for the backend, but it's mentioned that is worked around when using only one domain for the managing of the website (what we are doing)
At least the /data directory should be unique for each instance otherwise you'll end up with conflicts (all instances will write to the /data/umbraco/config file)
Recently come across a problem where a load balancing environment had the 'data' folder setup as a shared virtual IIS folder.
This causes a problem as the path UmbracoXmlDiskCacheFileName is being obtained through concatenation of the HttpRuntime.AppDomainAppPath and the disk cache file name, this results in an incorrect path being returned for the virtual directory:
load balanced server - do all files go on the share ?
We're experiencing extreme (30-90seconds) delays when publishing new pages and modifications on our server farm, on a labserver with the same website it takes a split second.
Is it possible that there are conflicts somewhere when there are multiple iis servers are using the same set of files (we have the entire website in a shared folder) that cause the save times to go up to about a minute instead of a split second?
The documentation talks about possible issues with lock files when using multiple url's for the backend, but it's mentioned that is worked around when using only one domain for the managing of the website (what we are doing)
all help is appreciated!
Comment author was deleted
Hi Rik,
At least the /data directory should be unique for each instance otherwise you'll end up with conflicts (all instances will write to the /data/umbraco/config file)
We just did a test with a complete copy of the files so we no longer use the share, but still publishing takes far to long...
any suggestions what else might be causing this?
could this be related?
http://umbraco.codeplex.com/WorkItem/View.aspx?WorkItemId=26370
is working on a reply...