Following are utilities included in the image to facilitate running commonly used
administration commands. Use of these utilities assumes you have exec access
to the container. Some of these utilities make use of the administration certs which have
full access to all indices and operations of the Elasticsearch cluster.
Run any REST command against the Elasticsearch endpoint
Example to retrieve the list of nodes
$ oc exec -c elasticsearch $POD -- es_util --query=_cat/nodes?pretty
Manually allocate replica shard to a given node in the Elasticsearch cluster. The node by default will be the one on which the command is executed. This command is used to explicitly reroute and allocate a replica shard.
Example:
$ oc exec -c elasticsearch $POD -- allocate-replica .kibana.02c55f18a892b365bcd1802db9e5c9df39c04674
Manually allocate a stale primary shard to a given node in the Elasticsearch cluster. The node by default will be the one on which the command is executed. This command is used to explicitly reroute and allocate a primary shard. NOTE: There is a risk of data loss when using this command
Example:
$ oc exec -c elasticsearch $POD -- allocate-stale-primary .kibana.02c55f18a892b365bcd1802db9e5c9df39c04674
Retrieve Elasticsearch logs from the log directory. This command defaults to retrieving
the file /elasticsearch/persistent/logging-es/logs/logging-es.log which may not be directed to
STDOUT by the logging configuration.
Example to follow the default file:
$ oc exec -c elasticsearch $POD -- logs -f
Manually move a shard to a given node in the Elasticsearch cluster.
Example:
$ oc exec -c elasticsearch $POD -- move-replica-shard .kibana.02c55f18a892b365bcd1802db9e5c9df39c04674 0 source-node target-node
List information about shards in the cluster
Example to find unassigned shards:
$ oc exec -c elasticsearch $POD -- shards | grep UNASSIGNED