Drupal-ims syncronization: develop plan to deal with purging the Drupal cache when (IMS) information has changed

14038
Reporter: ahahn
Assignee: bko
Type: Task
Summary: Drupal-ims syncronization: develop plan to deal with purging the Drupal cache when (IMS) information has changed
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2013-09-24 14:25:13.987
Updated: 2017-10-06 16:00:22.472
Resolved: 2017-10-06 16:00:22.456
        
Description: When e.g. address information changes in the IMS, or new contacts are added, they should make it through into the portal as soon as possible, but at least within about 24h. For this to happen, a) the Drupal cache needs to be updated, and b) the varnish cache has to be flushed. For b), see http://dev.gbif.org/issues/browse/PF-472. On a),
- clarify how long a drupal refresh takes and what exactly happens during that time - is the data truncated first so it iss temporarily gone? -> yes, the tables get dropped and during the next ~30 sec get re-filled with data
- until an automatic schedule can set up, the update has to be triggered manually (Drupal administrator rights required)
- set up an automatic update (probably once a day would be sufficient)]]>
    

Author: ahahn@gbif.org
Comment: Drupal update comes first, then Varnish
Created: 2013-09-24 14:25:51.481
Updated: 2013-09-24 14:25:51.481

Author: omeyn@gbif.org
Comment: [~cvizitiu@gbif.org] try the table renaming trick ala markus
Created: 2014-01-20 11:52:23.152
Updated: 2014-01-20 11:52:23.152

Author: bko@gbif.org
Comment: [~cvizitiu@gbif.org] Is this issue fixed?
Created: 2014-04-07 14:24:01.793
Updated: 2014-04-07 14:24:01.793

Author: bko@gbif.org
Comment: I'll make sure the coming IMS update process meets the requirement.
Created: 2014-10-21 11:45:22.058
Updated: 2014-10-21 11:45:22.058