And I just tried to follow your advice:
placed custom template in /etc/logstash/conf.d/templates/logstash2.json
{
"order" : 2,
"template" : "logstash-*",
"settings" : {
"index.number_of_replicas" : "4"
},
"mappings" : { }
}
then created a new index
curl -XPUT localhost:9200/logstash-111
and checked the result
# curl -XGET localhost:9200/logstash-111/_settings?pretty
{
"logstash-111" : {
"settings" : {
"index" : {
"uuid" : "l7HDeFfDS1arZr74ouwtyQ",
"analysis" : {
"analyzer" : {
"default" : {
"type" : "standard",
"stopwords" : "_none_"
}
}
},
"number_of_replicas" : "1",
"number_of_shards" : "5",
"refresh_interval" : "5s",
"version" : {
"created" : "1000051"
}
}
}
}
}
And it look like custom setting didn't override (default number of replicas
is 1)
On Friday, March 14, 2014 5:18:05 PM UTC+2, Sergey Zemlyanoy wrote:
>
> So is it enough data in my custom template in order to expect that new
> index will absorb its settings? Should I point out template's name in a
> dedicated field?
>
> On Thursday, March 13, 2014 9:55:13 PM UTC+2, Binh Ly wrote:
>>
>> You won't see your template in the list API, but if you create a new
>> index named logstash-<whatever>, it should take effect properly unless it
>> is overriden by another template with a higher order.
>>
>
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" 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/elasticsearch/ba98f7f5-5a25-4b1e-9da0-c564aaf8dc93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
