Symptoms

The CPU usage for BIG-IQ might spike during a search and the /var/log/searchd/eslognode.log file might log a warning similar to: [2018-05-24T20:41:34,332][WARN ][o.e.m.j.JvmGcMonitorService] [00000000-0000-0000-0000-222222222222] [gc][20354] overhead, spent [1.4s] collecting in the last [1.6s] [2018-05-24T20:41:35,949][WARN ][o.e.m.j.JvmGcMonitorService] [00000000-0000-0000-0000-222222222222] [gc][20355] overhead, spent [1.2s] collecting in the last [1.6s] [2018-05-24T20:41:37,280][WARN ][o.e.m.j.JvmGcMonitorService] [00000000-0000-0000-0000-222222222222] [gc][20356] overhead, spent [1.3s] collecting in the last [1.3s] Or returns one or more out of memory errors in the /var/log/searchd/eslognode.log, similar to the following: java.lang.OutOfMemoryError: Java heap space

Impact

BIG-IQ might become slow or unresponsive, or search results might lag well behind the changes to the data on the BIG-IQ. In the worst possible case, the situation might not resolve on its own.

Conditions

This can happen during large operation, such as importing a device or creating an application.

Workaround

None

Fix Information

None

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips