Bug ID 942185: Non-mirrored persistence records may accumulate over time

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1

Fixed In:
16.1.0, 16.0.1.2, 15.1.4

Opened: Sep 03, 2020

Severity: 2-Critical

Symptoms

Persistence records accumulate over time due to expiration process not reliably taking effect. The 'persist' memory type grows over time.

Impact

Memory pressure eventually impacts servicing of traffic in a variety of ways. Aggressive sweeper runs and terminates active connections. TMM may restart. Traffic disrupted while tmm restarts.

Conditions

-- Non-cookie, non-mirrored persistence configured. -- No high availability (HA) configured or HA connection permanently down. -- Traffic that activates persistence is occurring.

Workaround

None

Fix Information

Persistence records are now reliably expired at the appropriate time.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips