Bug ID 1677325: Pgsync OOM restart

Last Modified: Feb 11, 2025

Affected Product(s):
BIG_IP_NEXT(CM) TMOS(all modules)

Known Affected Versions:
20.3.0

Opened: Sep 23, 2024

Severity: 3-Major

Symptoms

Pgsync can have some OOM restarts due to low memory

Impact

No meaningful impact as pgsync will still run and sync the data

Conditions

CM backup/restore/upgrade can lead to pgsync OOM restart due to a sudden jump in postgreSQL data due to postgreSQL DB restore. also a very high number of records that has been already synced may cause OOM kill

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips