Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update connection cache to use a backing store per connection, rather than a shared backing store #699

Closed
kaidaguerre opened this issue Nov 1, 2023 · 0 comments

Comments

@kaidaguerre
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant