# Indexing strategy advice **URL:** \ **Category:** Elasticsearch\ **Created:** [November 24, 2014, 11:30pm UTC](https://discuss.elastic.co/t/indexing-strategy-advice/20923 "2014-11-24T23:30:57Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Justin\_Lintz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/justin_lintz/32/1090_2.png) [@Justin\_Lintz](https://discuss.elastic.co/u/Justin_Lintz)\ **Post date:** [November 24, 2014, 11:30pm UTC](https://discuss.elastic.co/t/indexing-strategy-advice/20923/1 "2014-11-24T23:30:57Z")
Hello all, We're currently evaluating how we should setup our index strategy for a new ES project. We're expecting about 1.5 million documents a month to be indexed and we're looking at creating Aliases with routing and filters to simulate per user indices. Should we just use one index for all this? I'm sure we'll be plenty fine for a while, but I was thinking into the future and if we want to roll data off or maybe move some of the older data into another cluster. If we did a time series index, how does that work with aliases? If we have thousands of aliases, at midnight of the time series rollover, do we need to update the thousands of aliases to point to the new index or can we have those aliases point to an index alias itself? Also is there a way to dynamically create aliases based on field data or is that something that needs to be done manually at this point? Thanks -- 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/56a99f81-73a6-4d86-9c28-b7c1092bda3b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/56a99f81-73a6-4d86-9c28-b7c1092bda3b%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [November 25, 2014, 12:46am UTC](https://discuss.elastic.co/t/indexing-strategy-advice/20923/2 "2014-11-25T00:46:30Z")
You'd be better off moving data into different indexes on the same cluster, then growing that cluster. Aliases are at an index level, so if you use time based indexes then you need to simply add the existing alias to that index, not update the alias. Check out > **[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. as it has good info. On 25 November 2014 at 10:30, Justin Lintz [jlintz@gmail.com](mailto:jlintz@gmail.com) wrote: > Hello all, > > We're currently evaluating how we should setup our index strategy for a > new ES project. > > We're expecting about 1.5 million documents a month to be indexed and > we're looking at creating Aliases with routing and filters to simulate per > user indices. > > Should we just use one index for all this? I'm sure we'll be plenty fine > for a while, but I was thinking into the future and if we want to roll data > off or maybe move some of the older data into another cluster. If we did a > time series index, how does that work with aliases? If we have thousands > of aliases, at midnight of the time series rollover, do we need to update > the thousands of aliases to point to the new index or can we have those > aliases point to an index alias itself? > > Also is there a way to dynamically create aliases based on field data or > is that something that needs to be done manually at this point? Thanks > > -- > 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/56a99f81-73a6-4d86-9c28-b7c1092bda3b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/56a99f81-73a6-4d86-9c28-b7c1092bda3b%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/56a99f81-73a6-4d86-9c28-b7c1092bda3b%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/56a99f81-73a6-4d86-9c28-b7c1092bda3b%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/CAF3ZnZkmE\_bKRK4tBMuVFNkBovv%2BB%2B0WtpwuAzT3sO%2BBdsijoQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAF3ZnZkmE_bKRK4tBMuVFNkBovv%2BB%2B0WtpwuAzT3sO%2BBdsijoQ%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, 12:47am UTC](https://discuss.elastic.co/t/indexing-strategy-advice/20923/3 "2017-07-06T00:47:54Z")