|
Wednesday 07 November 2007 3:01:56 pm
Hello. I am migrating an existing eZpublish site to a clustered environment and have it all pretty much working at this point except I am having some issues with the content view cache. It appears that no matter what I do, this cache is not being stored in the database. I have updated the file.ini.append.php to have the proper [ClusteringSettings] info, the images are all properly stored in the database and are functioning properly, etc. However, whenever I make content edits and publish the pages, the changes only show up on the server that I accessed the admin site on. The other server does not get its cache cleared until I manually log into the admin on that server and click the Clear Cache button (just content view cache will do the trick). I have verified that files are still being written to the var/cache/<siteaccess>/content folders on each server. I'm guessing it shouldn't do this if it's supposed to be using the database. I've gone over all the INI settings I can find, read the tutorials multiple times, etc., but I can't get this to work. Any suggestions? The client has a site that is both heavily trafficked and frequently updated (probably 20-30 nodes changed per day, some on an hourly basis). It's imperative to their operation that content changes be immediately reflected on the site. Thanks in advance!
|
