Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP AAM
Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2
Fixed In:
12.0.0, 11.6.0 HF6, 11.5.2, 11.4.1 HF6
Opened: Jul 09, 2014 Severity: 3-Major Related Article:
K16027
During periods of high velocity in the traffic pattern, datastor will seem to stop caching new objects.
For web sites that have a fairly static working set, this will reduce the efficacy of their caching by a percentage relative to the write reserve.
A traffic pattern that requires that a given percentage of the working set be displaced in order to move the cache content towards the new working set.
None.
Datastor will now reserve a given percentage of the obj table for the writing of new objects, forcing out objects to maintain this percentage. By default, if a new object cannot be created after a given period of time, datastor will log a message, then restart. Controlling how many contiguous failures before restart, the percentage of the obj table to reserve for writing, and how to restart datastor has been exposed as a new command line parameter. A change has been made to datastor to more readily allow for analyzing its core files.
Datastor will now reserve a given percentage of the obj table for the writing of new objects. By default, if a new object cannot be created after a given period of time, datastor will log a message, then restart. Controlling how many contiguous failures, the percentage of the obj table to reserve for writing, and how to restart datastor has been exposed as a new command line parameter.