Unassigned shards in Elasticsearch due to wrong shard allocation settings in OpenShift Container Platform 3.11

Solution Verified - Updated -

Issue

  • Unassigned shards with the reason INDEX_CREATED are not able to be allocated on any Elasticsearch node/pod.
  • Querying the cluster allocation explain API of Elasticsearch, shows shard allocation issue as listed:
$ oc exec  <es-pod-name> -- es_util --query=_cluster/allocation/explain?pretty
[..]
"allocate_explanation" : "cannot allocate because allocation is not permitted to any of the nodes"
"explanation" : "no allocations are allowed due to cluster setting [cluster.routing.allocation.enable=none]
[..]

Environment

  • Red Hat OpenShift Container Platform
    • 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