Elasticsearch pod fails to start on newly provisioned cluster

Solution In Progress - Updated -

Issue

  • The following exception error might be seen in the newly deployed Elasticsearch logging-es-data-master-ID-1-deploy pod:

    Elasticsearch logging-es-data-master-ID-1-deploy pods fail to start with "error: update acceptor rejected logging-es-data-master-mjksv8mi-1: pods for rc 'openshift-logging/logging-es-data-master-mjksv8mi-1' took longer than 1800 seconds to become available"

Environment

  • Red Hat OpenShift Container Platform (OCP) 3.11

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