Elasticsearch in OCP gets ReceiveTimeoutTransportException timed out after [5000ms]

Solution Verified - Updated -

Issue

  • Kibana cannot connect to Elasticsearch but all pods are running
  • See this message in the EFK (elasticsearch) logs
201X-XX-XX 21:08:54 INFO  transport:420 - [Her] failed to get node info for {#transport#-1}{127.0.0.1}{127.0.0.1:9300}, disconnecting...
ReceiveTimeoutTransportException[[][127.0.0.1:9300][cluster:monitor/nodes/liveness] request_id [26] timed out after [5000ms]]
    at org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:698)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)\

Environment

  • Red Hat OpenShift Container Platform
    • 3.6 and later
  • Elasticsearch / Fluentd / Kibana logging stack

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.