Operational Defect Database
BugZero found this defect 1614 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 828937
Some systems can experience periodic high IO wait due to AVR data aggregation
Last update date:
5/17/2024
Affected products:
BIG-IP
BIG-IP AVR
Affected releases:
13.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
13.1.3.3
14.0.0
14.0.0.1
14.0.0.2
Fixed releases:
16.0.0
15.1.0.5
14.1.2.5
13.1.3.4
Description:
Systems with a large amount of statistics data collected in the local database (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 the local database. ... Notice that large memory footprints, particularly for avrd might be a symptom for the phenomenon. ... Impact ... High IO can impact various processes on BIG-IP systems. ... Some of them can experience timeouts and might restart. ... The most effective workaround is to lower the amount of data collected by setting the 'avr.stats.internal.maxentitiespertable' DB variable to a lower value. ... The recommended values are 20000 (on larger, more powerful systems with more than 8 cores) or 2148 (on smaller systems). ... Note: After you lower the database value, continue to monitor the BIG-IP system for long I/O wait times and high CPU usage. ... If symptoms persist and the system continues to experience ...
