Elasticsearch becomes unavailable after upgrading to Red Hat OpenShift Container Platform to 3.9

Solution Verified - Updated -

Issue

  • After upgrading OCP to version 3.9.x, the elasticsearch pods do not enter a "Ready" state and thus elasticsearch becomes unavailable.
  • The KCS solution Deploying multiple Elasticsearch pods results in MasterNotDiscoveredException did not resolve the issue.
  • Elasticsearch pods yield the following error message:

        [2019-05-14 18:30:24,060][ERROR][com.floragunn.searchguard.action.configupdate.TransportConfigUpdateAction] [logging-es-data-master-7ti5fmmw] Failure while checking .searchguard.logging-es-data-master-7ti5fmmw index MasterNotDiscoveredException[null]
        MasterNotDiscoveredException[null]
        at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$5.onTimeout(TransportMasterNodeAction.java:234)
        at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:236)
        at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:816)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    

Environment

  • Red Hat OpenShift Container Platform (OCP)
    • 3.9

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