# How to: reindex data? **URL:** \ **Category:** Elasticsearch\ **Created:** [September 8, 2014, 6:58am UTC](https://discuss.elastic.co/t/how-to-reindex-data/19657 "2014-09-08T06:58:41Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Andrew\_Lakes](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@Andrew\_Lakes](https://discuss.elastic.co/u/Andrew_Lakes)\ **Post date:** [September 8, 2014, 6:58am UTC](https://discuss.elastic.co/t/how-to-reindex-data/19657/1 "2014-09-08T06:58:41Z")
Hey guys, 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? Thanks for response. -- 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/28fa5d25-0af2-4319-931d-7b1674e566ff%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/28fa5d25-0af2-4319-931d-7b1674e566ff%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![vineeth\_mohan\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vineeth_mohan_2/32/747_2.png) [@vineeth\_mohan\_2](https://discuss.elastic.co/u/vineeth_mohan_2)\ **Post date:** [September 8, 2014, 7:17am UTC](https://discuss.elastic.co/t/how-to-reindex-data/19657/2 "2014-09-08T07:17:35Z")
Hello Andrew , First use the remove field functionality in update API - > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. Then use update by query plugin ( use match\_all as query) to implement this to every documents - > **[GitHub - yakaz/elasticsearch-action-updatebyquery: ElasticSearch Update By...](https://github.com/yakaz/elasticsearch-action-updatebyquery)** > > ElasticSearch Update By Query action plugin. Contribute to yakaz/elasticsearch-action-updatebyquery development by creating an account on GitHub. Thanks Vineeth On Mon, Sep 8, 2014 at 12:28 PM, Andrew Lakes [alakes501@gmail.com](mailto:alakes501@gmail.com) wrote: > Hey guys, > > 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? > > Thanks for response. > > -- > 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/28fa5d25-0af2-4319-931d-7b1674e566ff%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/28fa5d25-0af2-4319-931d-7b1674e566ff%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/28fa5d25-0af2-4319-931d-7b1674e566ff%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/28fa5d25-0af2-4319-931d-7b1674e566ff%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAGdPd5kHaJXkOnDMU2n0S0KO5U%2Bz1jGALHunm21F%2BKOEeCK%2BGg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGdPd5kHaJXkOnDMU2n0S0KO5U%2Bz1jGALHunm21F%2BKOEeCK%2BGg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:03am UTC](https://discuss.elastic.co/t/how-to-reindex-data/19657/3 "2017-07-06T01:03:56Z")