Every time we perform graylog-ctl restart four more unassigned shards
appear:
Elasticsearch cluster is yellow. Shards: 20 active, 0 initializing, 0
relocating, 8 unassigned
graylog-ctl restart
Elasticsearch cluster is yellow. Shards: 20 active, 0 initializing, 0
relocating, 12 unassigned
Etc.
Using Graylog 2.0.2 EC2 Image on AWS.
Did not perform any additional configuration or maintenance. Is this a
symptom of something bad? How can it be fixed?
The only thing I could find on the internet about how to fix unassigned
shards is to perform this:
curl -XPUT 'localhost:9200/_settings' -d '{ "index" : {
"number_of_replicas" : 0}}'
This helped only first time, not anymore.
Please help!
--
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 graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/graylog2/cc65a871-5087-434a-982b-dbded2bf581d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
