If anyone has same problem. I found that once you run this, it will go back
to normal:
curl -XPUT 'localhost:9200/_settings' -d '{
"index" : {
"number_of_replicas" : 0
}
}'
(From this
page:
http://stackoverflow.com/questions/34611734/remove-unassigned-graylog2-index-shards-with-bash-in-a-loop)
On Wednesday, May 11, 2016 at 1:31:14 PM UTC+3, Joe K wrote:
>
> I installed 2.0.0 official EC2 AMI Image.
> Single, sandalone instance, not multiple ES instances in cluster.
>
> I did this two times and both times within one day from install I have
> notice in console:
> "Elasticsearch cluster unhealthy (RED). The Elasticsearch cluster state is
> RED which means shards are unassigned. This usually indicates a crashed and
> corrupt cluster and needs to be investigated."
>
> When I follow the link in that message it does not provide any useful info
> how to fix it.
>
> Can someone give instructions what to do please? For all us who are not
> experts in maintaining ElasticSearch clusters.
>
> - Graylog server seem to work fine with ES status RED. Does it even have
> to be investigated and fixed? Or it will get worse, like filling hard drive
> with data or something?
> - How to proceed, maybe there are steps, using CURL?
>
> Thank you!
>
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/graylog2/99a9aca4-d9df-4529-baf1-8271f59cd7ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
