Will the crash of jaeger components put my service in danger ? #2698
-
Hi, I'm wondering : Q1 : If the crash of jaeger components(like jaeger-agent, jaeger-collector or the backend storage) will put my service in danger? Q2 : If the jaeger-collector crashed, will jaeger-agent drop spans directly or store spans for a while ? If jaeger-agent store spans then how much spans will it stores ? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Q1: The jaeger Go client, which I'm most familiar with, sends (with some basic connection retry logic in the underlying UDP client), accumulates failure statistics and reports these stats to the agent on a subsequent successful send to the agent. In the event of a crash of jaeger-agent, jaeger-collector or backing store, the jaeger Go client will not crash, nor accumulate spans in memory (and retry at a later time). I don't have a good understanding of other language SDKs but would think they exhibit similar behaviour. Q2: If jaeger-collector crashes, the jaeger-agent will drop spans and does not retry. Dropped spans are logged by the agent and dropped span counts are reported against the |
Beta Was this translation helpful? Give feedback.
-
To complement @albertteoh's answer: no client should ever make your application fail. If they do, we consider it a bug. About the agent: when the collector isn't available, the gRPC client will retry the failed connections, so, the agent will keep some batches in memory until they eventually fail. |
Beta Was this translation helpful? Give feedback.
To complement @albertteoh's answer: no client should ever make your application fail. If they do, we consider it a bug. About the agent: when the collector isn't available, the gRPC client will retry the failed connections, so, the agent will keep some batches in memory until they eventually fail.