Operational Defect Database
BugZero found this defect 767 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 1073673
Prevent possible early exit from persist sync
Last update date:
5/8/2024
Affected products:
BIG-IP
BIG-IP DNS
Affected releases:
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
Fixed releases:
No fixed releases provided.
Description:
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 ... 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
