# Too many smaller indices. shards is creating issue

**URL:** <https://discuss.elastic.co/t/too-many-smaller-indices-shards-is-creating-issue/369271>\
**Category:** Elasticsearch\
**Created:** [October 23, 2024, 8:37am UTC](https://discuss.elastic.co/t/too-many-smaller-indices-shards-is-creating-issue/369271 "2024-10-23T08:37:19Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [October 23, 2024, 12:35pm UTC](https://discuss.elastic.co/t/too-many-smaller-indices-shards-is-creating-issue/369271/21 "2024-10-23T12:35:17Z")

</div>

If we are talking 25000 current aliases and expect this to grow I would recommend handling this through modification of the query instead. Having these aliases will make it appear just as it is today, but I have seen issues with large amounts of aliases (in older versions) so would stay clear of this.

[Previous page](https://discuss.elastic.co/t/too-many-smaller-indices-shards-is-creating-issue/369271.md?page=1)