Bug ID 2489061: Many empty records in an external datagroup can lower performance of some lookups and stall the tmm process

Last Modified: Nov 17, 2026

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

Known Affected Versions:
17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1, 17.1.3.2, 17.1.3.4, 17.1.3.5, 17.1.3.6, 17.1.3.7, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6, 17.5.1.8, 17.5.1.9, 17.5.1.10, 17.5.1.11, 21.0.0, 21.0.0.1, 21.0.0.2, 21.0.0.3

Opened: Aug 27, 2026

Severity: 3-Major

Symptoms

A tmm process thread may rarely stall while searching a datagroup. This may cause poor performance in the lookup, or a clock advanced log, or if severe enough tmm to be aborted by the software watchdog.

Impact

Possible poor performance in datagroup search for some keys. Possible tmm clock advanced logs. Possible abort of tmm process by software watchdog for missing heartbeat.

Conditions

Comma is the record separator in the external datagroup format. If the datagroup has very large numbers of empty records this may affect the performance of datagroup search. A typical record would look something like one of these: "key1" := "value1", key2, "key3" "key4" := "value4","key5" := "value5", If there are consecutive commas then empty records will be added to the datagroup hash So this would add three empty records as well entries for key6 and key7. key6,,,,key7, "key8" := "value8",, would add an empty record due to the additional comma.

Workaround

Do not include large numbers of empty records in the external datagroup.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips