Bug ID 844689: Possible temporary CPU usage increase with unusually large named.conf file

Last Modified: May 29, 2024

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1

Fixed In:
16.0.0, 15.1.2, 14.1.3.1

Opened: Oct 30, 2019

Severity: 3-Major

Symptoms

You might see occasional and temporary CPU usage increases when named.conf file is unusually large.

Impact

When a zone file is updated, a downstream effect is the ZoneRunner process to parse again the named.conf file. The parsing of an unusually large file may cause a temporary increase in CPU usage.

Conditions

Unusually large named.conf file and zones are checked for updates (when the SOA expires).

Workaround

None.

Fix Information

ZoneRunner does not issue a reload command when zones are checked for updates, so no CPU usage increases occur.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips