Replies: 1 comment
-
Linkerd doesn't enforce an idle timeout on opaque connections--if the application holds the connection open, linkerd should as well. I'd recommend inspecting the proxy logs on both the client and server, which may include messages indicating a connection error. If there are not, you might try running with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm having issues with our cluster using linkerd2. The app connects to Redis to subscribe and publish events. But after 10 minutes, the connection is closed, forcing a reconnect.
Running the app locally using the same Redis cluster works as expected, but its' closed every 10m in the k8s cluster. I checked the outbound Load Balancer resource in Azure and it's set up to timeout after 30 minutes.
Is there a setting in linkerd to control this behaviour? I think that in old versions we had
idleTtlSecs
but I can't find it in the docs for the latest version.Beta Was this translation helpful? Give feedback.
All reactions