[AWS EKS] Extremely frequent "transport is closing" and "transport closed by client" log messages with Helm chart v1.0.2 and OpenSearch

[mwojtas1]

I'm using the Jaeger Helm chart version 1.0.2, deployed on AWS EKS, and integrated with AWS OpenSearch as the storage backend. I'm seeing two types of log messages being printed to the logs extremely frequently (up to ~1000 times per minute):

"msg":"[transport] [server-transport 0xc009fe5860] loopyWriter exiting with error: connection error: desc = \"transport is closing\""}
"msg":"[transport] [server-transport 0xc011aeeb60] loopyWriter exiting with error: transport closed by client"

To troubleshoot, I increased the number of replicas for jaeger-collector from 1 to 2, but this did not reduce the frequency of the messages.

Environment:

• Jaeger Helm chart: 1.0.2
• Platform: AWS EKS
• Storage backend: AWS OpenSearch
• Logging level: default

Questions:

• Are these messages expected under normal operation?
• Could this indicate a deeper problem (e.g., connection mismanagement, health probe misconfiguration, gRPC misbehavior)?