There has been a long going issue, that if aggressive caching is used, the Cache is always expired if a client checks in.
This is due to a bug, that clears the cache before retrieving the old information, which leads to the new groups assigned by a probe to be always new, as olddata is always [].
This should fix performance for servers that are utilizing the "aggressive" caching mode.
There has been a long going issue, that if aggressive caching is used, the Cache is always expired if a client checks in. This is due to a bug, that clears the cache before retrieving the old information, which leads to the new groups assigned by a probe to be always new, as olddata is always [].
This should fix performance for servers that are utilizing the "aggressive" caching mode.