# AutoScale elasticsearch **URL:** \ **Category:** Elasticsearch\ **Created:** [May 11, 2015, 2:07am UTC](https://discuss.elastic.co/t/autoscale-elasticsearch/23601 "2015-05-11T02:07:56Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![John\_S](https://avatars.discourse-cdn.com/v4/letter/j/a9a28c/32.png) [@John\_S](https://discuss.elastic.co/u/John_S)\ **Post date:** [May 11, 2015, 2:07am UTC](https://discuss.elastic.co/t/autoscale-elasticsearch/23601/1 "2015-05-11T02:07:56Z")
Hi, Currently am having a cluster with 4 nodes provisioned in Aws Ec2. Occasionally there were some issue happened like disk space utilization and cpu utilization, which impacted the cluster, then manually add new disk or create additional nodes for handling load. I was investigating if there is an automated option, something like elasticsearch cluster if there is an high disk utilization, or other option like horizontal scaling for high cpu issue(like changing the instance type to a higher instance capacity with cpu/memory). There is an Autoscale option from Aws services for high cpu utilization, but just thinking if there is any other options available from cluster level. Am trying to build a solution to avoid any downtime. Let me know if anyone have any approach to handle these and possible impacts doing so. Note: understand adding one more data nodes will re-balance the shards in the cluster. Regards John ## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/) 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/9b8708d0-e1f0-4c7b-bba1-b663c68a4741%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9b8708d0-e1f0-4c7b-bba1-b663c68a4741%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:** [May 11, 2015, 2:52am UTC](https://discuss.elastic.co/t/autoscale-elasticsearch/23601/2 "2015-05-11T02:52:24Z")
You can certainly use AWS autoscaling groups to accomplish things, but there is nothing native in ES to do it. On 11 May 2015 at 12:07, John S [bunix1@gmail.com](mailto:bunix1@gmail.com) wrote: > Hi, > > Currently am having a cluster with 4 nodes provisioned in Aws > Ec2. Occasionally there were some issue happened like disk > space utilization and cpu utilization, which impacted the cluster, then > manually add new disk or create additional nodes for handling load. > > I was investigating if there is an automated option, something like > elasticsearch cluster if there is an high disk utilization, or other > option like horizontal scaling for high cpu issue(like changing the > instance type to a higher instance capacity with cpu/memory). > > There is an Autoscale option from Aws services for high cpu utilization, > but just thinking if there is any other options available from cluster > level. > > Am trying to build a solution to avoid any downtime. Let me know if > anyone have any approach to handle these and possible impacts doing so. > Note: understand adding one more data nodes will re-balance the shards in > the cluster. > > Regards > John > > ## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/) > > 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/9b8708d0-e1f0-4c7b-bba1-b663c68a4741%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9b8708d0-e1f0-4c7b-bba1-b663c68a4741%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/9b8708d0-e1f0-4c7b-bba1-b663c68a4741%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/9b8708d0-e1f0-4c7b-bba1-b663c68a4741%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/) 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/CAEYi1X88CH0KUCs81qn2boR9conPZa61F5Pv50EhVOFaLAdcMQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X88CH0KUCs81qn2boR9conPZa61F5Pv50EhVOFaLAdcMQ%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:14am UTC](https://discuss.elastic.co/t/autoscale-elasticsearch/23601/3 "2017-07-06T00:14:43Z")