The nodeId of 71 doesn't really make any sense (it's not a content node, in fact looking in the database there is no node with an id of 71!) and there is no instruction to process, the slave server cannot get past the instruction before this and so I think it is failing on this specific instruction.
Not sure if this will be useful due to the age of the thread, but may come in use for someone else finding this topic.
As I develop a 3rd party package for Umbraco and recently found out it doesn't work correctly in a load balance setup due to the caching invloded in the package, I've come across this within the Documentation
In theory, it should be safe to delete the record within the table and perform an app pool restart on each server within the load balance cluster, as the app pool restart would invalidate any caches on the server.
From looking at the data stored, whatever wrote the record into the table is inheriting the IJsonCacheRefresher which more information can be found in the link provided earlier
Cache Instructions that break the cache between load balanced servers
Can anyone elaborate on this cache instruction?
The nodeId of
71doesn't really make any sense (it's not a content node, in fact looking in the database there is no node with an id of 71!) and there is no instruction to process, the slave server cannot get past the instruction before this and so I think it is failing on this specific instruction.Hey Simon
Not sure if this will be useful due to the age of the thread, but may come in use for someone else finding this topic.
As I develop a 3rd party package for Umbraco and recently found out it doesn't work correctly in a load balance setup due to the caching invloded in the package, I've come across this within the Documentation
In theory, it should be safe to delete the record within the table and perform an app pool restart on each server within the load balance cluster, as the app pool restart would invalidate any caches on the server.
From looking at the data stored, whatever wrote the record into the table is inheriting the
IJsonCacheRefresherwhich more information can be found in the link provided earlierRegards,
Joshua
is working on a reply...