Nodes recycle/restart due to a JVM memory issue. The issue is caused by high memory consumption by the Shazzam sensor in the Discovery sensor's jobs.

Steps to Reproduce


Although there are no definitive steps to reproduce the issue, the following steps might cause the problem:

  1. Navigate to Discovery > Discovery Schedules.
  2. Add the column Shazzam batch size.
  3. For all the schedulers, change the Shazzam batch size from 500 to 5000.


The following workarounds are available:

  • Reduce the number of IP addresses in problematic schedules (split into multiple schedules)
  • Do not exclude IPs from a large IP range - use multiple IP ranges instead
  • Do not include a large number of small IP ranges - simplify by aggregating consecutive ranges where possible
  • Reduce the number of MID servers being used by problematic schedules
  • Contact Customer Support for a patch to the Shazzam sensor script

After you have applied one or more of these workarounds, turn on Discovery to test.

Related Problem: PRB660591

Seen In

Calgary Patch 4
Eureka Patch 11 Hot Fix 2
Eureka Patch 13 Hot Fix 2
Fuji Patch 10
Fuji Patch 12 Hot Fix 1
Fuji Patch 6
Fuji Patch 8
Fuji Patch 9
Geneva Patch 1
Geneva Patch 1 Hot Fix 5
Geneva Patch 3 Hot Fix 1
Geneva Patch 4
Geneva Patch 5
Geneva Patch 7 Hot Fix 5
Helsinki Patch 5

Fixed In

Fuji Patch 13
Geneva Patch 3 Hot Fix 7
Geneva Patch 5

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2017-07-05 15:57:08