818 views

Description

The Import Set Deleter job cleans records in the import tables. A problem that was fixed in Fuji addressed out of memory exceptions that arise from MultipleDelete, which Import Set Deleter utilizes. However, the fixes did not completely prevent memory concerns for the Import Set Deleter job.

Steps to Reproduce

  1. Create a large number of import sets (for example, 10,000).
    Each import set needs to have a nominal load (for example, 2,000) of records to be imported.
  2. Navigate to System Import Sets > Scheduled Cleanup.
  3. Change Days from 7 to 0.
  4. Click Execute now.
    The deleter job runs on all import sets. Note that memory consumption increases substantially while the deleter job is running. The job is loading GlideRecords, but it only needs the names of staging tables.

Workaround

  1. Navigate to Script Includes > ImportSetCleaner.
  2. Change the line: 
    this.cleanedImportSetRowTables.push(gr.table_name);
    to
    //this.cleanedImportSetRowTables.push(gr.table_name);

Notice that the line is now commented out.


Related Problem: PRB709421

Seen In

Dublin Patch 8 Hot Fix 4
Fuji Patch 12 Hot Fix 1
Fuji Patch 13 Hot Fix 1
Geneva Patch 6 Hot Fix 2
Geneva Patch 7
Geneva Patch 7 Hot Fix 2
Geneva Patch 8
Geneva Patch 9
Helsinki Patch 2
Helsinki Patch 3
Helsinki Patch 3 Hot Fix 2
Helsinki Patch 4
Helsinki Patch 5

Fixed In

Geneva Patch 10
Helsinki Patch 6
Istanbul

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2017-04-21 06:22:46
Published:2016-09-01