In the /config/umbracoSettings.config area there are settings for load balanced nodes.
When updating the media in the media section, does this use the umbracoSettings.config to update the memory cache across the nodes in the cluster?
<!-- distributed calls make umbraco use webservices to handle cache refreshing --> <distributedCall enable="true"> <!-- the id of the user who's making the calls --> <!-- needed for security, umbraco will automatically look up correct login and passwords --> <user>0</user> <servers>
<!-- add ip number or hostname, make sure that it can be reached from all servers -->
This is only for content, sorry no Media. Maybe you can use the Media_Aftersave event to trigger the save action and Distribute the Media item yourself?
"The cache for a specific item is flushed when you save a media item
in the media section. The cached item is also removed when you delete
it. The media items are being cached in the Application items
(HttpContext.Current.Application).."
So this cache flushing is only handled on the web node handling the update and all other web nodes will remain out-of-date (having a stale version in memory)?
That isn't answering the question. To clarify, my media files are being distributed, the moment I upload them, onto the other NLB nodes via Domain File Replication. Its not the file system I am asking about, but the xml chunk "in-memory" that stores the node/data. Will this memory data be updated on other NLB nodes in the web cluster when the media is updated?
From what I've discovered so far this solution CAN NOT work in any environment were multiple web nodes are required due to a failure to update the file reference in memory on each node.
NLB - Does this work with the umbracoSettings.config?
In the /config/umbracoSettings.config area there are settings for load balanced nodes.
When updating the media in the media section, does this use the umbracoSettings.config to update the memory cache across the nodes in the cluster?
<!-- distributed calls make umbraco use webservices to handle cache refreshing -->
<distributedCall enable="true">
<!-- the id of the user who's making the calls -->
<!-- needed for security, umbraco will automatically look up correct login and passwords -->
<user>0</user>
<servers>
<!-- add ip number or hostname, make sure that it can be reached from all servers -->
<server>node1</server><server>node2</server>
</servers>
</distributedCall>
Cheers.
HI,
This is only for content, sorry no Media. Maybe you can use the Media_Aftersave event to trigger the save action and Distribute the Media item yourself?
Cheers,
Richard
"The cache for a specific item is flushed when you save a media item in the media section. The cached item is also removed when you delete it. The media items are being cached in the Application items (HttpContext.Current.Application).."
So this cache flushing is only handled on the web node handling the update and all other web nodes will remain out-of-date (having a stale version in memory)?
Yes - the memory cache is updated when you publish a new / updated node. Media needs to be on a shared volume / disk / sync'd.
That isn't answering the question. To clarify, my media files are being distributed, the moment I upload them, onto the other NLB nodes via Domain File Replication. Its not the file system I am asking about, but the xml chunk "in-memory" that stores the node/data. Will this memory data be updated on other NLB nodes in the web cluster when the media is updated?
From what I've discovered so far this solution CAN NOT work in any environment were multiple web nodes are required due to a failure to update the file reference in memory on each node.
is working on a reply...