Cache and EZFind

Next topic

Author	Message
Bryan Ruiz	Tuesday 27 January 2009 7:35:36 am I am using a cache server that makes a cached copy of the ezpublish site which has a "time to live" and an api that can be called to update the cache. There is a 7 minute lag that these cache servers need to update. I am having a hard time visualizing what will happen when this mechanism is combined with ezfind. Are there any implications that a set of cache servers would cause when, lets say, a page gets edited and the cache needs to be updated. What about if I run updatesearchindexsolr.php as a cron every 5 minutes? Or maybe this wouldnt be a good idea because if its ran every 5 minutes, it may not complete in time, so lets say 20 minutes? Thanks, Bryan Ruiz
Jérôme Vieilledent	Saturday 21 February 2009 5:10:54 am Hi Bryan As far as I know, eZFind (at least the latest 2.0 version) updates its index each time you publish/delete an object. So you don't have to run <i>updatesearchindexsolr.php</i> as a CRON...
Emmanuel Courmont	Sunday 05 April 2009 2:05:23 pm Hi Bryan, You only need to run a cron job if the indexing is delayed. You can find this setting in site.ini [SearchSettings] DelayedIndexing=enabled The indexcontent.php is part of the cronjob by default. See cronjob.ini [CronjobSettings] ScriptDirectories[]=cronjobs ... Scripts[]=indexcontent.php
Geoff Bentley	Wednesday 08 April 2009 9:52:30 pm The cronjobs have only recently been fixed in the SVN repo of eZ Find, and have been split into two - <i>ezfindexcontent.php</i> and <i>ezfoptimizeindex.php</i>. This allows the more server-intensive optimization to be actioned once or twice a day. <i>settings/cronjob.ini.append.php</i> has also been added to ezfind - if you are using the stable 2.0 version you will need to create this yourself and add to the default cronjob script list or to the CronjobPart-frequent, e.g: <?php /* [CronjobSettings] ExtensionDirectories[]=ezfind Scripts[]=ezfindexcontent.php */ ?>