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
The fix is to add a configurable timeout for Redis operations - if any operation takes over this time, we should close the connection and consider the operation failed (falling back to either the actual auth hook, or the actual request, whichever makes suitable fallback option at this time)
Keywords
redis webhook auth caching
The text was updated successfully, but these errors were encountered:
Version Information
Server Version: 2.37.0
Environment
EE
What is the current behaviour?
Currently, we have an issue where Redis connections can end up “dead” and just fail to return any data given some TLS settings
This manifests in very slow lookups to the auth hook cache. This is in context to webhook auth caching feature.
What is the expected behaviour?
The fix is to add a configurable timeout for Redis operations - if any operation takes over this time, we should close the connection and consider the operation failed (falling back to either the actual auth hook, or the actual request, whichever makes suitable fallback option at this time)
Keywords
redis webhook auth caching
The text was updated successfully, but these errors were encountered: