[exporter/loadbalancingexporter] - Static resolver dropping the data when one of the host is not healthy

[ramanjaneyagupta]

Component(s)

exporter/loadbalancing

Describe the issue you're reporting

Collector Version: v0.96.0
Configuration:

exporters:
  loadbalancing:
    routing_key: "traceID"
    protocol:
      otlp:
        timeout: 1s
    resolver:
      static:
        hostnames:
        - backend-1:4317
        - backend-2:4317
        - backend-3:4317
        - backend-4:4317 
service:
  pipelines:
    traces:
      receivers:
        - otlp
      exporters:
        - loadbalancing

If one of the host is down in the static list, loadbalancingexporter unable to send the data to healthy host. Instead sending the data to health host it is dropping the data on the floor.

[github-actions]

Pinging code owners:

• exporter/loadbalancing: @jpkrohling

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[jpkrohling]

If one of the host is down in the static list, loadbalancingexporter unable to send the data to healthy host. Instead sending the data to health host it is dropping the data on the floor.

That's the expected behavior, at least for the moment. When using a static list, we expect the hosts to be available to receive the data, even if they are temporarily unavailable (for instance, by using a Kubernetes Statefulset). If your static list isn't that static, the solution is to use a DNS resolver, where the DNS is updated to list only the healthy nodes (like a Kubernetes headless service).