Blocker Current Behavior:
When the connection to Redis is interrupted, backend-listener, backend-worker or backend-cron may not be able to automatically re-stablish the connection to Redis again, and therefore, the following issues may be experienced:
- Internal Server errors in the 3scale admin portal when creating products/accounts.
- Unexpected 403 responses returned by APIcast gateway.
Expected Behavior:
Any clients connecting to Redis should be able to re-establish a new connection when the previous one has broken.
It seems this was introduced by the change to the redis async client in 2.15
- duplicates
-
THREESCALE-11528 Backends Redis connection re-establishment
-
- Closed
-
- is blocked by
-
-
- Closed
-
- relates to
-
-
- Closed
-
- links to