Elasticsearch in OpenShift Service Mesh has yellow status due to shard allocation failure in RHOCP 4

Solution Verified - Updated -

Issue

  • Elasticsearch in OpenShift Service Mesh has yellow status.
  • Elasticesearch pod has below log message reporting a shard allocation failure.

    shard has exceeded the maximum number of retries [5] on failed allocation attempts - manually call [/_cluster/reroute?retry_failed=true] to retry, [unassigned_info[[reason=ALLOCATION_FAILED], failed_attempts[5], delayed=false, details[failed shard on node [2eWoWRKwQcmfsVrh_dthuQ]: failed to create shard, failure IllegalStateException[environment is not locked]; nested: AccessDeniedException[/elasticsearch/persistent/elasticsearch/data/nodes/0/node.lock]; ], allocation_status[no_attempt]]]"
    
  • The log says Elasticsearch has stopped trying to allocate this shard automatically.

Environment

  • Red Hat OpenShift Container Platform (OCP) 4.14
  • Red Hat OpenShift Service Mesh (OSSM) 4.14
  • Elasticsearch logging in OSSM

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