# Cluster with a lot of aliases **URL:** \ **Category:** Elasticsearch\ **Created:** [October 30, 2013, 5:33am UTC](https://discuss.elastic.co/t/cluster-with-a-lot-of-aliases/14165 "2013-10-30T05:33:04Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Oleksiy\_Kovyrin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oleksiy_kovyrin/32/1901_2.png) [@Oleksiy\_Kovyrin](https://discuss.elastic.co/u/Oleksiy_Kovyrin)\ **Post date:** [October 30, 2013, 5:33am UTC](https://discuss.elastic.co/t/cluster-with-a-lot-of-aliases/14165/1 "2013-10-30T05:33:04Z")
Hey guys, We at Swiftype use ElasticSearch a lot and absolutely love its power and flexibility. Thanks for the great product! We use aliases a lot on our clusters to implement shared indexes for multiple customers and in some cases we could have hundreds and thousands of aliases on an index. It was never a huge problem, but recently we've started seeing more and more strange java memory usage issues (LOTS of garbage is being generated while processing cluster state changes: adding/removing indexes and aliases) on a cluster with 800 shards (700+indexes) and more than 30000 aliases on one one of the indexes. I do understand that that is most probably a really unusual edge case for elasticsearch, but still - is there anything you could recommend for reducing the amounts of garbage generated in memory while processing cluster state updates in this case? P.S. I'm trying to create a reproducible test case that would show this issue on an arbitrary cluster, will let you know how it goes. -- Oleksiy Kovyrin [http://kovyrin.net/](http://kovyrin.net/) -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\ **Post date:** [November 14, 2013, 8:45am UTC](https://discuss.elastic.co/t/cluster-with-a-lot-of-aliases/14165/2 "2013-11-14T08:45:23Z")
Hey, thanks for kind words, highly appreciated. regarding your problems: We are using google guava maps classes (which are immutable and thus a lot of object creations are going on). There was a recent change (in the 0.90.7 release), which does not do this anymore in case of mapping updates, so we have a base of classes we possibly could use here as well. May I ask, what your update patterns are? You are adding/removing indices/aliases all the time and therefore have cluster state updates as well? How big is your cluster state? Oh, and we love reproducible test-cases 🙂 --Alex On Wed, Oct 30, 2013 at 6:33 AM, Oleksiy Kovyrin [alexey@kovyrin.net](mailto:alexey@kovyrin.net) wrote: > Hey guys, > > We at Swiftype use Elasticsearch a lot and absolutely love its power and > flexibility. Thanks for the great product! > > We use aliases a lot on our clusters to implement shared indexes for > multiple customers and in some cases we could have hundreds and thousands > of aliases on an index. It was never a huge problem, but recently we've > started seeing more and more strange java memory usage issues (LOTS of > garbage is being generated while processing cluster state changes: > adding/removing indexes and aliases) on a cluster with 800 shards > (700+indexes) and more than 30000 aliases on one one of the indexes. > > I do understand that that is most probably a really unusual edge case for > elasticsearch, but still - is there anything you could recommend for > reducing the amounts of garbage generated in memory while processing > cluster state updates in this case? > > P.S. I'm trying to create a reproducible test case that would show this > issue on an arbitrary cluster, will let you know how it goes. > > -- > Oleksiy Kovyrin > [http://kovyrin.net/](http://kovyrin.net/) > > -- > 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). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:07am UTC](https://discuss.elastic.co/t/cluster-with-a-lot-of-aliases/14165/3 "2017-07-06T02:07:15Z")