Elasticsearch pods are not up and running

Solution In Progress - Updated -

Issue

  • After following installation of Cluster Logging the elasticsearch pod are not up and running.
  • The elasticsearch pod is reporting the following errors:

    [2020-07-30 22:23:51,112][INFO ][container.run            ] Setting heap dump location /elasticsearch/persistent/heapdump.hprof
    [2020-07-30 22:23:51,114][INFO ][container.run            ] ES_JAVA_OPTS: ' -Xms8192m -Xmx8192m -XX:HeapDumpPath=/elasticsearch/persistent/heapdump.hprof -Dsg.display_lic_none=false -Dio.netty.recycler.maxCapacityPerThread=0 -Dio.netty.allocator.type=unpooled'
    [2020-07-30 22:23:51,114][INFO ][container.run            ] Checking if Elasticsearch is ready
    OpenJDK 64-Bit Server VM warning: If the number of processors is expected to increase from one, then you should configure the number of parallel GC threads appropriately using -XX:ParallelGCThreads=N
    [2020-07-30 22:28:55,137][ERROR][container.run            ] Timed out waiting for Elasticsearch to be ready
    cat: elasticsearch_connect_log.txt: No such file or directory
    

Environment

  • Red Hat OpenShift Container Platform
    • 4.4.9
  • VMware VSphere

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content