Last Modified: Nov 07, 2022
See more info
Known Affected Versions:
6.1.0, 7.0.0, 184.108.40.206, 220.127.116.11, 7.1.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 7.1.6, 188.8.131.52, 7.1.7, 184.108.40.206, 220.127.116.11, 7.1.8, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 7.1.9, 220.127.116.11, 18.104.22.168, 22.214.171.124
Opened: Aug 02, 2019
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