Last Modified: Jul 12, 2023
Affected Product(s):
BIG-IQ AppIQ
Known Affected Versions:
7.1.0, 7.1.0.1, 7.1.0.2, 7.1.0.3, 7.1.6, 7.1.6.1, 7.1.7, 7.1.7.1, 7.1.7.2, 7.1.8, 7.1.8.1, 7.1.8.2, 7.1.8.3, 7.1.8.4, 7.1.8.5, 7.1.9, 7.1.9.7, 7.1.9.8, 7.1.9.9
Opened: Aug 13, 2020 Severity: 3-Major
The UI takes a long time to render pages that show active alerts related information.
Slowness of the UI in pages with active alert related information
The system is configured with a large number (thousands) of alerts
Configure the query service to get alerts from in-memory storage (used by the health calculator process) instead of from elastic-search. - In /var/config/appiq/queryservice/bin/run_queryservice_bigiq.sh, add "eventstore-alarms" to the "spring_profile" list. - restart the query service using "bigstart restart appiquery" command. Impact of workaround: There is a risk that a large amount of alerts will fill up the memory of appiqquery, hence it is important to increase its JVM memory, by editing the "/etc/biq_daemon_provision.json" file. - If the alerts count on the UI is greater than 10k - the recommendation for 64GB systems is to increase the appiqquery JVM memory allocation from 800MB to 1.2GB while reducing the restjavad JVM memory allocation from 20000MB to 19600MB. - If the alerts count on the UI is greater then 25k - the recommendation for 64GB system's is to increase the appiqquery JVM memory from 800MB to 2GB For 32GB systems, the same values should apply. The only potential issue here is that it would not be safe to reduce the allocated JVM memory of restjavad in case the system has a large number of ASM devices with many ASM entities since, during import/discovery of these devices high memory consumption is expected by restjavad. Internal testing showed high memory consumption by restjavad with ~160 ASM devices and overall of 1000 policies. If this is not the case for your environment then you can safely modify the restjavad memory. Once memory changes are done, query service and restjavad must be restarted, in order for the JVM memory changes to take effect, by running the command "bigstart restart restjavad appiqquery".
None