Bug ID 436830: Rendezvous Name Mismatch

Last Modified: Mar 21, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP WAM(all modules)

Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5

Fixed In:
12.0.0, 11.6.0 HF6, 11.4.1 HF6

Opened: Nov 06, 2013
Severity: 3-Major
Related AskF5 Article:
K15621

Symptoms

Datastor service crashes with a name mismatch.

Impact

This will cause datastor to crash on a name mismatch.

Conditions

This can occur when rendezvous is being utilized on boxes that are being subjected to a very high traffic velocity, and a domain size that requires disc utilization.

Workaround

Reduce the amount of cache traffic and the total size of the cache domain.

Fix Information

Modify the active policies on the effected box to exclude from caching those classes of object that have a low popularity, and especially those that either change quickly on the server, or are requested rarely.

Behavior Change