[英]AWS ECS cluster auto-scaling vs service auto-scaling
this is my first time using amazon ecs service.这是我第一次使用亚马逊 ecs 服务。
I have searched online for awhile to understand auto-scaling with ecs services.我在网上搜索了一段时间以了解使用 ecs 服务的自动缩放。
I found there are two options to auto-scale my application.我发现有两个选项可以自动扩展我的应用程序。 But, There are some I don't understand.但是,有一些我不明白。
First is Service auto scaling which track the cpu/memory metric from cloudWatch and increase the task number accordingly.首先是服务自动缩放,它跟踪来自 cloudWatch 的 cpu/内存指标并相应地增加任务数量。
Second is cluster auto scaling which needs to create auto scaling resource, create capacity provider and so on.二是集群伸缩,需要创建伸缩资源,创建容量提供者等。 But, in Tutorial: Using cluster auto scaling , it can run the task definition without service.但是,在教程:使用集群自动扩展中,它可以在没有服务的情况下运行任务定义。 But it also seems increasing the task number in the end.但它似乎也最终增加了任务数量。
So what's the different and 'pros and cons' between them?那么它们之间有什么不同和“利弊”呢?
I will try to explain briefly.我将尝试简要解释一下。
Scaling: Ultimately, We will be scaling the tasks just by setting desired no of tasks between min and max tasks, based on CPU or any other metric of individual task.缩放:最终,我们将根据 CPU 或单个任务的任何其他指标,通过在最小任务和最大任务之间设置所需的任务数来缩放任务。 This is called service auto scaling.这称为服务自动缩放。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.