-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Replies: 1 comment · 5 replies
-
Hi @asheeshv! To dig into the details of exactly why the proxy is doing failfast here, I'd recommend turning up the log level to trace https://linkerd.io/2.11/tasks/modifying-proxy-log-level/ and looking at the logs around when the proxy first starts reporting failfast. This should give some clue as to why failfast is getting triggered. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Thanks for the response, @adleong. Much appreciated! I turned up the log levels to debug and there's a lot logging statements. I will turn it down to trace then. Mulitple of my proxies reported fail-fast, but I'm guessing that since they are dependent, if one of them failed, the other ones fail as well becaue of a ripple effect. I'll post some data after turning the logs down to trace, and see if I can extract more info. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hello @adleong, I turned the trace logs on one of the service proxies, and here's the data as follows: |
Beta Was this translation helpful? Give feedback.
All reactions
-
I do see these errors in my service container now: |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hello @adleong, Any inputs on this. I'd appreciate your help! |
Beta Was this translation helpful? Give feedback.
All reactions
-
@adleong Here are some of the logs I see after turning debug logs in my proxy:
My question is that is there a way I can determine what is the proxy that's getting disconnected and which service container is it associated with? I don't see any fail-fast errors in any of the other proxies my api-gateway is connected to. Shouldn't I be seeing errors there as well? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello folks,
I've integrated linkerd in our microservices deployment, and am running into HTTP fail-fast errors, which only occur when I increase a certain load to my system My server application uses gRPC for communicating with the external clients and internal services.
When I start with 50 clients, it runs fine, but when I increase the number of connections to 50, linkerd-proxy starts reporting http logical in failfast.
However, I don't see any errors in my application service code, so I'm really puzzled as to what's going on.
Here are the linkerd-proxy logs from my api-gateway service, which shows Http logical in failfast even though the rest of the pods are still up and running.
I'm using v2.11.4 of linkerd. Really appreciate any inputs or pointers as we are closing in our development timeline and need to wrap up load-testing. It'd be unfortunate to not use linkerd if this turns out to be a bigger issue, so would appreciate any guidance here.
I also took logs out of the linkerd-proxy-injector and saw these
I see these failures for failed to resolve A record: no record found for name: linkerd-dst-headless.linkerd.svc.cluster.local. type: AAAA class: IN.
What does this mean? Is this some sort of a configuration failure, where the proxy fails to come up.
Beta Was this translation helpful? Give feedback.
All reactions