we encountered a small problem with our new elasticsearch cluster.
Logstash indexed a whole lot of useless fields like "<133>Sep 7 02:42:43
server apache2-access: accesstime" due to a misconfiguration from us and
now we got about 95000 useless fields that slow down Kibana a lot, cause
kibana is loading /_all/_mapping everytime you load a dashboad in order to
get the right fields for the table-panel
I read a bit and saw that deleting fields only is available with reindex
the whole index.
We use the version 1.3.2 of elasticsearch and our indices got the default
names from logstash ("logstash-2014.09.08").
So for example, how do i manage the reindex that index? I´ve read sth about
making aliases and point the alias to the old index and than reindex - but
how is that exactly working?
we encountered a small problem with our new elasticsearch cluster.
Logstash indexed a whole lot of useless fields like "<133>Sep 7 02:42:43
server apache2-access: accesstime" due to a misconfiguration from us and
now we got about 95000 useless fields that slow down Kibana a lot, cause
kibana is loading /_all/_mapping everytime you load a dashboad in order to
get the right fields for the table-panel
I read a bit and saw that deleting fields only is available with reindex
the whole index.
We use the version 1.3.2 of elasticsearch and our indices got the default
names from logstash ("logstash-2014.09.08").
So for example, how do i manage the reindex that index? I´ve read sth
about making aliases and point the alias to the old index and than reindex
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.