-
Notifications
You must be signed in to change notification settings - Fork 80
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
LD relay fails to reconnect to Redis after Redis restarts #207
Comments
Hi @carlosjgp, really appreciate this report. We'll look into it and get back to you. Filed internally as 178424. |
@carlosjgp in your report when you mention "after Redis has restarted", how exactly were you simulating that? Scaling the stateful set back down and up again shows the relay reconnecting appropriately. |
@keelerm84 you can just terminate the POD
or as you mention
and after a while |
Hmmm, I have tried reproducing this with both options, and each worked as expected with the relay re-establishing connection to the redis instance. You state that the relay fails to reconnect; looking at yours logs, can you confirm if it successfully establishes connection initially before restarting redis? How are you installing the redis helm chart? Are you using the default parameters, or are you overriding some of them, like the password? And how are you injecting that information in the relay proxy helm chart? |
Closing due to inactivity. Please feel free to re-open if you continue experiencing this issue. |
https://support.launchdarkly.com/hc/en-us/requests/new
Describe the bug
LD relay fails to connect to Redis after Redis has restarted
To reproduce
16.5.0
Expected behavior
Fast automatic recovery whether this is fallback to "relay without store" or reconnect to Redis
Logs
If applicable, add any log output related to your problem.
SDK version
Language version, developer tools
N/A
OS/platform
Additional context
possibly related to redis/go-redis#1737
Using Sentinel could mitigate this
#114
The text was updated successfully, but these errors were encountered: