issue with distributed environments, clustered databases and 'GetById'?
umbraco version 7.0.4
hey out there,
hit a weird one today with 'GetById' not returning (or appearing not to return...) content from the database.
our set up is 2 web servers talking to a database cluster. we've got umbraco pushing to the 2 web servers using the 'distributedCall' feature.
the site code was using this code to pull the content from the database:
var node = new ContentService().GetById(theNodeToGet);
even though the content was saved and published in umbraco, server 1 returned older content than server 2.
so we changed the code to:
var node = Umbraco.TypedContent(theNodeToGet);
hey presto, both servers returned the same content!
according to this 'GetById' should pull from the database and 'TypedContent' should pull from the cache.
i know it's difficult to advise without knowing the specific environment and view logs etc but is there a known issue with distributed environments, clustered databases and 'GetById'?
issue with distributed environments, clustered databases and 'GetById'?
umbraco version 7.0.4
hey out there,
hit a weird one today with 'GetById' not returning (or appearing not to return...) content from the database.
our set up is 2 web servers talking to a database cluster. we've got umbraco pushing to the 2 web servers using the 'distributedCall' feature.
the site code was using this code to pull the content from the database:
var node = new ContentService().GetById(theNodeToGet);
even though the content was saved and published in umbraco, server 1 returned older content than server 2.
so we changed the code to:
var node = Umbraco.TypedContent(theNodeToGet);
hey presto, both servers returned the same content!
according to this 'GetById' should pull from the database and 'TypedContent' should pull from the cache.
i know it's difficult to advise without knowing the specific environment and view logs etc but is there a known issue with distributed environments, clustered databases and 'GetById'?
any comments would be grand!
cheers,
jake
is working on a reply...