DNS reslove error

[yphanikumar1995]

(check apply)

• [ ] read the contribution guideline
• [ ] (optional) already reported 3rd party upstream repository or mailing list if you use k8s addon or helm charts.

Problem

... We are getting below error no address for cl-es-master.commonservices.svc.cluster.local (Resolv::ResolvError)"

If we exec into kubernetes pod and do the nslookup or dig it is resloving the ip address

Can you give the solution and let me know why this error coming

Steps to replicate

Either clone and modify https://gist.github.com/pitr/9a518e840db58f435911

OR

Provide example config and message

Expected Behavior or What you need to ask

...

Using Fluentd and ES plugin versions

• OS version
• Bare Metal or within Docker or Kubernetes or others?
• Fluentd v0.12 or v0.14/v1.0
  • paste result of fluentd --version or td-agent --version
• ES plugin 3.x.y/2.x.y or 1.x.y
  • paste boot log of fluentd or td-agent
  • paste result of fluent-gem list, td-agent-gem list or your Gemfile.lock
• ES version (optional)
• ES template(s) (optional)

[joelsdc]

Did you ever figure out what causes this? I'm seeing the same issue...

[eli-gc]

Running into the same error. Seems to resolve if we restart fluentd pod, but I'm guessing it happens again over time.

[vishalk663]

Hi We are also facing the same issue repeatedly. Our EFK cluster is deployed in kubernetes cluster. we are getting the (Resolv::ResolvError) when connecting to elasticsearch service. because of this issue we lost some chunks which was not pushed into elasticsearch.

we are using file buffer with below configuration.

      <buffer>
        @type file
        path /var/log/xxxx/xxxx/
        total_limit_size 64GB
        chunk_limit_size 8MB
        flush_mode interval
        flush_interval 5s
        flush_thread_count 8
        retry_type exponential_backoff
        retry_timeout 6h
        retry_max_interval 30

Thanks

[vishalk663]

Can someone please help here?