# Auto Scaling Group r b/w the Data Nodes? **URL:** \ **Category:** Elasticsearch\ **Created:** [March 11, 2019, 9:33am UTC](https://discuss.elastic.co/t/auto-scaling-group-r-b-w-the-data-nodes/171715 "2019-03-11T09:33:21Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![rahulkumar1](https://avatars.discourse-cdn.com/v4/letter/r/a4c791/32.png) [@rahulkumar1](https://discuss.elastic.co/u/rahulkumar1)\ **Post date:** [March 11, 2019, 9:33am UTC](https://discuss.elastic.co/t/auto-scaling-group-r-b-w-the-data-nodes/171715/1 "2019-03-11T09:33:22Z")
Would it be recommended to place a Autoscaling Group and a LoadBalancer (ALB) b/w the Data Nodes in AWS ? What could be the pro's and cons of this approach. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 11, 2019, 11:19am UTC](https://discuss.elastic.co/t/auto-scaling-group-r-b-w-the-data-nodes/171715/2 "2019-03-11T11:19:12Z")
No. It's not recommended. You should control that manually IMHO. Adding a new node is an important decision. Specifically if you have a huge volume of data. ---
**Author:** ![rahulkumar1](https://avatars.discourse-cdn.com/v4/letter/r/a4c791/32.png) [@rahulkumar1](https://discuss.elastic.co/u/rahulkumar1)\ **Post date:** [March 11, 2019, 3:35pm UTC](https://discuss.elastic.co/t/auto-scaling-group-r-b-w-the-data-nodes/171715/3 "2019-03-11T15:35:04Z")
Thanks dadoonet !! What would be a deciding factor in determining the number of Data Nodes ? ---
**Author:** ![mjunaidmuzammil](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mjunaidmuzammil/32/56910_2.png) [@mjunaidmuzammil](https://discuss.elastic.co/u/mjunaidmuzammil)\ **Post date:** [March 11, 2019, 7:49pm UTC](https://discuss.elastic.co/t/auto-scaling-group-r-b-w-the-data-nodes/171715/4 "2019-03-11T19:49:53Z")
In my opinion, number of shards should be the major deciding factor for the number of data nodes. As a rule of thumb, there should be around 20-25 shards per 1GB heap. There is a max heap limit for a data node which is approx 32G ([https://www.elastic.co/guide/en/elasticsearch/guide/current/heap-sizing.html#compressed\_oops](https://www.elastic.co/guide/en/elasticsearch/guide/current/heap-sizing.html#compressed_oops)). So typically, you shouldn't exceed beyond 800 shards on a single data node. In cases where you have larger data volume requirement, you can expand the attached disk volumes. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [March 11, 2019, 11:18pm UTC](https://discuss.elastic.co/t/auto-scaling-group-r-b-w-the-data-nodes/171715/5 "2019-03-11T23:18:09Z")
In addition to the previous answer, may I suggest you look at the following resources about sizing: [https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing](https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing) > **[How many shards should I have in my Elasticsearch cluster? | Elastic](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster)** > > Elasticsearch is a very versatile platform, that supports a variety of use cases, and provides great flexibility around data organisation and replication strategies. This flexibility can however somet... https://www.slideshare.net/slideshow/embed_code/key/vR0XKDq4TGa77z And [https://www.elastic.co/webinars/using-rally-to-get-your-elasticsearch-cluster-size-right](https://www.elastic.co/webinars/using-rally-to-get-your-elasticsearch-cluster-size-right) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 8, 2019, 11:22pm UTC](https://discuss.elastic.co/t/auto-scaling-group-r-b-w-the-data-nodes/171715/6 "2019-04-08T23:22:48Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.