Bug ID 1073673: Prevent possible early exit from persist sync

Last Modified: Dec 05, 2024

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

Known Affected Versions:
16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1

Fixed In:
17.1.2

Opened: Jan 18, 2022

Severity: 3-Major

Symptoms

When a new GTM is added to the Sync group, it takes a significant amount of time, and the newly added GTM won't become ready.

Impact

Clients of the BIG-IP GTM do not receive an answer, and application failures may occur.

Conditions

-- GTMs in a cluster with a large number of persist records -- A new GTM device is added

Workaround

None

Fix Information

None

Behavior Change

A new DB variable gtm.persistsynctimespan is introduced. This setting controls the period for the persist records sent to a GTM peer as part of the persist sync operation. Increase the value if the peers are stuck waiting for persist record sync. Default value: 10 Minimum value: 1 Maximum value: 200

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips