F5 | 1517469

When monitoring pool members using the LTM or GTM mssql (Microsoft SQL Server) monitor, memory and CPU consumption by the database monitor daemon (DBDaemon) process may increase over time. ... The increase in memory consumption by the DBDaemon process may be gradual and relatively steady over a long period of time, until memory consumption nears an RSS size of approximately 150MB. ... At that point, CPU consumption may start increasing rapidly. ... These increases may continue until the DBDaemon process restarts, restoring normal memory and CPU consumption until the cycle begins again. ... Impact ... As more objects remain in memory in the DBDaemon process, database monitor query operations may complete more slowly, which may cause pool members to be marked Down incorrectly. ... As memory and CPU consumption reach critical levels, more pool members may be marked Down. ... While the DBDaemon process restarts, all pool members monitored by database monitors (mssql, mysql, oracle, post...