ThriftSender received a span that was too large

[Avers90]

Describe the bug ThriftSender received a span that was too large, size = 278492, max = 64842 in the app logs.

To Reproduce Steps to reproduce the behavior:

1. Install Jaeger Operator in Kubernetes
2. Add sidecar container in app with jaeger-client
3. In app logs i see "ThriftSender received a span that was too large, size = 278492, max = 64842"

Version (please complete the following information):

• OS: Linux
• Jaeger version: 1.27
• Deployment: Kubernetes

Additional context On the app side in logs i see "ThriftSender received a span that was too large, size = 278492, max = 64842". In this document https://www.jaegertracing.io/docs/1.28/performance-tuning/#adjust-server-queue-sizes I read, in order to avoid this error on the application side, you need to change the parameter for sidecar jaeger-agent - --processor.jaeger-binary.server-max-packet-size

How can i change processor.jaeger-binary.server-max-packet-size in sidecar jaeger-agent?

In Kubernetes sidecar jaeger-agent i add with:

metadata:
  name: <app_name>
  annotations:
    "sidecar.jaegertracing.io/inject": "true"

[AlKapkone]

I've got the same issue.

[frzifus]

Hey, this can be specified using the JaegerCR. e.g.

apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
  name: simplest
spec:
  agent:
    options:
      processor:
         jaeger-binary:
           server-max-packet-size: 1234

You can verify your option using kubectl describe pod ${pod-name}.

Containers:
  jaeger-agent:
    Args:
      --processor.jaeger-binary.server-max-packet-size=1234

Can we close this issue?

[Avers90]

I can't testing it now. But i think u can close this issue.

[frzifus]

@AlKapkone can you verify it?

[AhHa45]

I would like to understand why a span is too large?