# Alias with high number of indices

**URL:** <https://discuss.elastic.co/t/alias-with-high-number-of-indices/204008>\
**Category:** Elasticsearch\
**Created:** [October 17, 2019, 8:57am UTC](https://discuss.elastic.co/t/alias-with-high-number-of-indices/204008 "2019-10-17T08:57:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ctombaugh](https://avatars.discourse-cdn.com/v4/letter/c/f07891/32.png) [@ctombaugh](https://discuss.elastic.co/u/ctombaugh)\
**Post date:** [October 17, 2019, 8:57am UTC](https://discuss.elastic.co/t/alias-with-high-number-of-indices/204008/1 "2019-10-17T08:57:07Z")

</div>

I have a collection of around 100,000,000 documents, which consists of a few thousand subsets (each tens to millions of documents). Most of these subsets are regularly updated (wipe and replace, a few times per month). Until now my strategy has been to first remove the old version of a subset and then index the newer version, but this means that during indexing (which can take up to half an hour) the subset is not or only partially available. Would it be a better strategy to create an index for each subset and just update the alias after a newer version of a subset has been indexed? Any caveats?

Thanks

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 14, 2019, 8:59am UTC](https://discuss.elastic.co/t/alias-with-high-number-of-indices/204008/2 "2019-11-14T08:59:57Z")

</div>

Closed on November 14, 2019, 8:59am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.