Hi Joe,
the reconfigure script should not do any Elasticsearch actions other then a
restart when there is a configuration change. You could see at the end of
the output if ES was restarted or not.
If you want to set the number of replicas to 0, you can use advanced
attributes like documented here:
http://docs.graylog.org/en/2.0/pages/installation/graylog_ctl.html#advanced-settings
The attribute would be: custome_attributes -> graylog-server ->
elasticsearch_replicas -> 0
Cheers,
Marius
On Monday, 30 May 2016 16:32:17 UTC+2, Joe K wrote:
>
>
> 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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/graylog2/697a9a4a-8da7-4c42-a624-27ae0cc9d36e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.