Elasticsearch cluster unhealthy (RED) - how to fix?

Question

graylog

Good afternoon.
Downloaded and deployed the ova-version of graylog2
After launch, a warning appeared:

Elasticsearch cluster unhealthy (RED) (triggered a day ago)
The Elasticsearch cluster state is RED which means shards are unassigned. This usually indicates a crashed and corrupt cluster and needs to be investigated. Graylog will write into the local disk journal. Read how to fix this in the Elasticsearch setup documentation.

I did not find how to fix it in the docks, only "red is bad" is written.
Please tell me how can I fix this problem? Only 1 input added

Answer 1

You most likely need to set up your ElasticSearch cluster. By default, the cluster does not work with a single node.
To work with a single node, you need to apply the following settings:

index.number_of_shards: 1
index.number_of_replicas: 0
node.local: true
discovery.zen.ping.multicast.enabled: false
discovery.zen.minimum_master_nodes: 1
node.max_local_storage_nodes: 1

Beware, the solution is not for production!

Answer 2

Good afternoon,
you need to look at the logs for an
offhand answer, maybe your ES version is not supported in graylog2, there are restrictions there.