After starting use of this module we are seeing alot of java / kafka errors from linkerd.
java.net.ConnectException: Connection refused
WARN 0620 18:19:05.201 UTC kafka-producer-network-thread | producer-1: Error in I/O with localhost/127.0.0.1
at java.lang.Thread.run(Thread.java:748)
at org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:191)
E 0620 18:18:52.913 UTC THREAD36 TraceId:b34e5cf7b68e40ef: service failure: com.twitter.finagle.CancelledConnectionException
Config:
telemetry:
- kind: io.zipkin.http
host: :9411
initialSampleRate: 0.02
Where Collector-Domain.com points at an AWS NLB and targets are jaeger-collector containers running in ECS.
This issue happens intermittently on hosts and seems to only be solved by a restart of linkerd. Any insight would be appreciated.
After starting use of this module we are seeing alot of java / kafka errors from linkerd.
java.net.ConnectException: Connection refusedWARN 0620 18:19:05.201 UTC kafka-producer-network-thread | producer-1: Error in I/O with localhost/127.0.0.1at java.lang.Thread.run(Thread.java:748)at org.apache.kafka.clients.producer.internals.Sender.run(Sender.java:191)E 0620 18:18:52.913 UTC THREAD36 TraceId:b34e5cf7b68e40ef: service failure: com.twitter.finagle.CancelledConnectionExceptionConfig:
telemetry:
host: :9411
initialSampleRate: 0.02
Where Collector-Domain.com points at an AWS NLB and targets are jaeger-collector containers running in ECS.
This issue happens intermittently on hosts and seems to only be solved by a restart of linkerd. Any insight would be appreciated.