-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a way to disable replica shard via configuration? #2727
Comments
That value is set on index creations, however replica shards can be configured via elasticsearch. See here for changing replica counts: http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/replica-shards.html |
Thx. Yes, of course I can make PUT request with template in initialization script. Do you think it would be better if you locate it as config such way instead of current hardcoded approach: https://github.com/logstash-plugins/logstash-output-elasticsearch/blob/master/lib/logstash/outputs/elasticsearch/elasticsearch-template.json |
You'd probably be better off asking that question in the logstash channel on freenode |
it seems you I did not explain it well. I mean, that would be great have have index template file (e.g. elatiscsearch-template.js) somewhere outside of.create_kibana_index.js. |
Hi,
When I create a simple configuration with one node I have 1 unassigned ".kibana" replica shard, it affects my ES cluster health. As I know, replica shard cannot be located in primary shard node so I have no other way apart from to delete it. So, in this case I would to specify explicitly in kibana.yml whether I need replica shard or not.
I found this value hardcoded
Does it makes sense? Was this setting has been hardcoded by design?
The text was updated successfully, but these errors were encountered: