Template is placed in /etc/elasticsearch/config/templates/logstash2.json
[root@logstash elasticsearch]# ls -la /etc/elasticsearch/
total 56
drwxr-xr-x 3 root root 4096 Feb 26 13:26 .
drwxr-xr-x. 99 root root 12288 Feb 22 03:37 ..
drwxr-xr-x 3 root root 4096 Feb 26 11:27 config
rw-rr- 1 root root 12686 Feb 26 11:52 elasticsearch.yml
rw-rr- 1 root root 12662 Jan 20 14:24 elasticsearch.yml.rpmsave
rw-rr- 1 root root 1512 Jan 15 18:05 logging.yml
Also I leaved in default state elasticsearch.yml file, so all path
variables are commented.
After service restart I don't see any new index template. What am I doing
wrong? Is the template path wrong?
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.
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-, it should take effect properly unless it is
overriden by another template with a higher order.
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-, it should take effect properly unless it
is overriden by another template with a higher order.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.