Operational Defect Database
BugZero found this defect 1067 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 1025089
Pool members marked DOWN by database monitor under heavy load and/or unstable connections
Last update date:
5/1/2024
Affected products:
BIG-IP
BIG-IP GTM
BIG-IP LTM
Affected releases:
12.1.5.3
12.1.6
13.1.3.2
13.1.3.3
13.1.3.4
13.1.3.5
13.1.3.6
13.1.4
13.1.4.1
13.1.5
13.1.5.1
14.1.2.3
Fixed releases:
No fixed releases provided.
Description:
Bug ID 1025089: Pool members marked DOWN by database monitor under heavy load and/or unstable connections ... a momentary loss of connectivity. ... This is more likely to occur when a database monitor is used to monitor a GTM pool member instead of an LTM pool member, due to differences between how monitors are configured for GTM versus LTM. - Under certain conditions, DBDaemon CPU use may increase indefinitely. ... Impact ... -- High CPU utilization is observed on control plane cores. -- The database monitoring daemon (DBDaemon) may restart unexpectedly, causing GTM or LTM pool members monitored by a database monitor to be marked DOWN temporarily. -- GTM or LTM pool members monitored by a database monitor may be marked DOWN temporarily if the network connection to the database server is dropped or times out. ... Perform one of the following actions: -- Configure the database (mssql, mysql, oracle, postgresql) monitor with a "count" value of "1". ... This prevents the caching or reu...
