377 views

Description

IMPORTANT -----------------------------

The fix for this PRB was to have the data collection jobs canceled if memory exceeded a threshold while they were processing. This was checked into Helsinki, however, was reverted via PRB712738 (DataCollector should not use glide.memory.watcher.log_threads_threshold to kill the job) in HP3HF12 & HP6+ due to problems.  Due to this, memory issues can still occur while processing data collection jobs. 

------------------------------------------------

Scheduled data collections from Performance Analytics can cause instances to run out of memory when there are a large number of records in the indicator source. Users will notice being logged off or instance unavailability. The severity of performance degradation depends on the frequency of the scheduled data collection jobs.

Steps to Reproduce

Run a data collection job for an indicator source with more than 2 million records.

Workaround

There are several ways to reduce memory usage during data collection.

  • Configure your indicator sources so that a smaller number of records are included. For example, add additional filter conditions to the indicator source.
  • Create additional indicator sources instead of including more records in a single indicator source.
  • Set the property com.snc.pa.dc.max_row_count_indicator_source to a lower value. This limits the maximum number of records included in any indicator source. By default, this property allows 50,000 records per indicator source.
  • Set the property com.snc.pa.dc.max_records to a lower value to limit the maximum number of records collected for snapshots. By default, this property allows 5000 records to be collected. You can also clear the Collect records field for indicators to disable snapshots for those indicators.
  • Reduce the number of breakdowns for collected indicators. You can exclude breakdowns in the data collection job or clear the Collect breakdown matrix field for indicators to disable 2nd-level breakdowns for those indicators.

Related Problem: PRB650867

Seen In

Eureka Patch 13
Eureka Patch 13 Hot Fix 6
Eureka Patch 6
Eureka Patch 7 Hot Fix 6
Fuji Patch 13 Hot Fix 1
Fuji Patch 2
Fuji Patch 3
Fuji Patch 5
Fuji Patch 6
Fuji Patch 9 Hot Fix 1
Geneva Patch 6 Hot Fix 2
Geneva Patch 7

Fixed In

Helsinki

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2017-07-24 23:47:07
Published:2015-12-09