You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In pipes, we are seeing issues with high numbers of connecitons where the cached credentials are not always cleared from the cache.
Currently the connection cache uses a shared backing store for all connections, and the entries for a given connection tagged with the connection. go-cache allows deletion of all cache entries with a given tag which is how the conneciotn cache is cleared currently.
However it seems the tagging fails under certain circumstances, meaning the cache deletion sometimes does not work, resulting in expired credentials being kept in the cache.
So, instead, use a cache store per connection and just clear the whole cache when clearing for a connection
The text was updated successfully, but these errors were encountered:
In pipes, we are seeing issues with high numbers of connecitons where the cached credentials are not always cleared from the cache.
Currently the connection cache uses a shared backing store for all connections, and the entries for a given connection tagged with the connection. go-cache allows deletion of all cache entries with a given tag which is how the conneciotn cache is cleared currently.
However it seems the tagging fails under certain circumstances, meaning the cache deletion sometimes does not work, resulting in expired credentials being kept in the cache.
So, instead, use a cache store per connection and just clear the whole cache when clearing for a connection
The text was updated successfully, but these errors were encountered: