(PANGAEA et al.) Excessive synchronizing with the GBRDS after sync. with the indexing database is finished

12687
Reporter: jlegind
Assignee: kbraak
Type: Bug
Summary: (PANGAEA et al.) Excessive synchronizing with the GBRDS after sync. with the indexing database is finished
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2013-02-01 12:08:48.453
Updated: 2013-02-01 14:44:01.275
Resolved: 2013-02-01 14:44:01.247
        
Description: [11:48:54] Kyle: it's currently true that after a synchronization finishes successfully, a sync with registry by organization is scheduled. The current reasoning is that:
          // the Portal's data_provider id will have been populated for the organization in the Registry
          // the Portal's data_resource id will have been populated now for the resource in the Registry
          // so update all bioDatasources having that organization as their publisher

- This eats up system resources when a large number of datasets are scheduled.]]>
    

Author: kbraak@gbif.org
Created: 2013-02-01 14:44:01.274
Updated: 2013-02-01 14:44:01.274
        
An automatic registry synchronization after index synchronization was unnecessary since the registry is now polled directly for any information needed during synchronization.

So that you are also aware [~ahahn@gbif.org], revision 1814 fixes this problem. I need to redeploy a new version of the hit scheduler so that this goes live.