Bug ID 828937: Some systems can experience periodic high IO wait due to AVR data aggregation

Last Modified: Jan 22, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP AVR(all modules)

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 15.0.0, 15.0.1, 15.0.1.1, 15.1.0

Opened: Sep 19, 2019
Severity: 2-Critical
Related AskF5 Article:
K45725467

Symptoms

Systems with a large amount of statistics data collected in the local DB (i.e., systems not working with BIG-IQ) can have high IO Wait CPU usage, peaking at 10 minutes, 1 hour, and 24 hours. This is caused by the data aggregation process that is running on local DB.

Impact

High IO can impact various processes on BIG-IP systems. Some of them can experience timeouts and can be restarted.

Conditions

-- The BIG-IP system is collecting statistics locally (i.e., not sending data to BIG-IQ or another external device). -- There is a large amount of statistics data.

Workaround

The most effective workaround is to lower the amount of data collected by setting the 'maxentitiespertable' DB variable to a lower value. The recommended values are 20000 (on larger, more powerful systems with more than 16 cores) or 2148 (on smaller systems).

Fix Information

None

Behavior Change