Bug ID 812097: Elasticsearch may crash and create core file when too little memory is allocated to BIG-IQ

Last Modified: Nov 07, 2022

Affected Product(s):
BIG-IQ Platform(all modules)

Known Affected Versions:
6.1.0, 7.0.0,,, 7.1.0,,,, 7.1.6,, 7.1.7,,, 7.1.8,,,,,, 7.1.9,,,

Opened: Aug 02, 2019

Severity: 4-Minor


If a BIG-IQ node, either console or DCD, has less than 32GB of RAM available (per node), the ElasticSearch instance on that node may crash and generate core file.


The ElasticSearch log prints the following message in certain situations, e.g., large volume of stats collected: java.lang.OutOfMemoryError: GC overhead limit exceeded When the ElasticSearch is out of memory, it is not available for querying and/or storing new statistics.


1. Install BIG-IQ with data collection, where at least one node (either console ore DCD) has 16GB RAM. 2. Using the BIG-IQ UI monitor several BIG-IP devices.


1. Increase the memory of the BIG-IQ console and DCD nodes to 32GB RAM each. 2. Verify that the ElasticSearch cluster is healthy again and statistics are displayed under the BIG-IQ monitoring tab

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips