Bug ID 931353: Table bloat causes high availability (HA) to fail

Last Modified: Jul 12, 2023

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

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: Jul 27, 2020

Severity: 3-Major

Symptoms

Failover does not complete fully. You see an error in /var/log/restjavad.0.log: Failed query '$skip=0&$top=150&$filter=name+eq+'*'&$orderby=name+asc&kind=cm:adc-core:working-config:ltm:pool:adcpoolstate&parentContext=https://localhost/mgmt/cm/adc-core/working-config/ltm/pool&modules=adc-core' - org.postgresql.util.PSQLException: ERROR: could not write to tuplestore temporary file: No space left on device You also see diskmonitor errors: err diskmonitor: 011d0004:3: Disk partition /var has only 7% free

Impact

HA configuration is removed, failover does complete.

Conditions

This can occur if /var reaches 90% full, which can be caused by excessive table bloat in the Postgres database.

Workaround

Performing VACUUM FULL manually on DB will clean up bloat but can be disruptive to system. For more information on this procedure, see K18484011: BIG-IQ Reclaim unused disk space from postgres database, available at https://support.f5.com/csp/article/K18484011

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips