Finally I managed to solve it! It was caused by wrong template path -
/etc/elasticsearch/config/templates/sometemplate.json
It should be /etc/elasticsearch/templates/sometemplate.json
Thanks a lot!
On Friday, March 14, 2014 8:41:26 PM UTC+2, Binh Ly wrote:
>
> I can think of 2 reasons:
>
> 1)
I can think of 2 reasons:
1) When you start elasticsearch, it is not pointing to the conf directory
that your are using
or
2) There is another template that overrides yours
I'm thinking #1 is more likely. How are you running ES, i.e., how is it
installed and ran?
--
You received this messag
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 localhos
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 in
You won't see your template in the list API, but if you create a new index
named logstash-, 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 unsu
Dear all,
In order to overwrite some index settings I created a custom template:
{
"logstash2" : {
"order" : 1,
"template" : "logstash-*",
"settings" :
{ "index.number_of_replicas" : "0" }
}
}
Template is placed in /etc/elasticsearch/config/templates/logstash2.json
[root@logstash elastics
