[Bug] Elasticsearch cluster is not able to initialize in RHOCP 4.6

Solution Verified - Updated -

Issue

  • After upgrading RHOCP cluster to 4.6 and upgrading clusterlogging operator to v4.6, the logging stack works fine for some days and then the Elasticsearch cluster is not able to initialize.
  • Elasticsearch pods stuck at 1/2 Running:
elasticsearch-cdm-agramz9f-1-59d9686859-8h2mb  1/2    Running    0         1h15m
elasticsearch-cdm-agramz9f-2-6c6dc6c754-l9wnf  1/2    Running    0         1h15m
elasticsearch-cdm-agramz9f-3-768f9d486c-gf5dc  1/2    Running    0         1h15m
  • Elasticsearch pod logs show below error messages:
2021-01-27T07:10:44.461449322Z [2021-01-27T07:10:44,460][ERROR][c.a.o.s.a.BackendRegistry] [elasticsearch-cdm-agramz9f-1] Not yet initialized 
2021-01-27T07:11:05.618668540Z [2021-01-27T07:11:05,618][ERROR][c.a.o.s.a.BackendRegistry] [elasticsearch-cdm-agramz9f-1] Not yet initialized 
2021-01-27T07:11:14.412493347Z [2021-01-27T07:11:14,412][ERROR][c.a.o.s.a.BackendRegistry] [elasticsearch-cdm-agramz9f-1] Not yet initialized 
2021-01-27T07:11:35.618385546Z [2021-01-27T07:11:35,618][ERROR][c.a.o.s.a.BackendRegistry] [elasticsearch-cdm-agramz9f-1] Not yet initialized

Environment

  • Red Hat OpenShift Container Platform [RHOCP]
    • 4.6

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