In some environments, Security Explorer, Capacity Overview, and other UI pages in SSP may load very slowly or fail to display. In some cases, partial data may appear after a long delay.
During this issue, the following errors can be observed in the postgresql-ha-postgresql-0 pod logs:
Additional PostgreSQL logs may indicate that VACUUM is unable to clean up a large number of dead tuples:
SSP5.0,
SSP5.1
This issue occurs when the PostgreSQL shared memory directory (/dev/shm) becomes full.
As a result:
PostgreSQL cannot resize shared memory segments
VACUUM FULL cannot complete
Dead tuples accumulate
This is commonly seen when:
Large tables exist (normalizedcomputeconfig, normalizedgroupconfig)
Vacuum cannot acquire required locks
Parallel workers increase shared memory pressure
SSP 5.1.1 includes a partial mitigation to reduce the frequency of this issue.
- This is not a permanent fix. It temporarily reduces memory pressure but does not fully prevent /dev/shm exhaustion. Root cause analysis is still ongoing.
- Manual workaround – contact Broadcom ANS Support for assistance if needed.