阅读背景:

自动扩展EC2或其他云计算基础架构有哪些实际限制?

来源:互联网 

I was curious if anyone has experimented with auto scaling web or db tier in EC2 or other cloud computing infrastructure? It seems theoretically possible, but I am curious what the practical limitations are/maybe.

我很好奇是否有人在EC2或其他云计算基础设施中尝试自动扩展Web或db层?这似乎在理论上是可行的,但我很好奇实际的限制是什么/可能。

Thanks!

3 个解决方案

#1


We are also starting to look at auto-scaling.

我们也开始关注自动缩放。

The first candidate approach is to use Amazon's ELB (Elastic Load Balancer) and Cloud Front. However, our traffic is a web service. Caller's frequently send the 100-Continue http message, and ELB cannot understand that message. There's no word yet from Amazon on when that might be fixed. Also, there are a number of complaints in the Amazon forums about ELB not handling heavy load.

第一种候选方法是使用亚马逊的ELB(Elastic Load Balancer)和Cloud Front。但是,我们的流量是一种Web服务。呼叫者经常发送100-Continue http消息,而ELB无法理解该消息。亚马逊还没有关于什么时候可以修复的消息。此外,亚马逊论坛上有很多关于ELB没有处理重负荷的投诉。

LigHTTPD 1.5 looks like a promising partial solution, in that it can detect when an instance is not functioning and transparently take it out of the rotation, and can be dynamically reconfigured without restarting the load balancer.

LigHTTPD 1.5看起来像是一个有前途的部分解决方案,因为它可以检测实例何时无法运行并透明地将其从旋转中取出,并且可以动态重新配置而无需重新启动负载均衡器。

There are a number of commercial solutions as well. We will probably have a look at Right Scale.

还有许多商业解决方案。我们可能会看看Right Scale。

#2


This is more of a question than an answer, but I'm about to start experimenting with autoscaling myself (most likely using the Amazon CloudFront facilities) and am thinking that instance startup time will be a factor. I've noticed that a new EC2 instance can take from 5 to 20 minutes to start up, so it's not as if you can instantly add more capacity when your load increases; it seems like you would need one or more idle instances to be running and ready to pick up increased load.

这不仅仅是一个问题,而是一个答案,但我即将开始尝试使用自动缩放(最有可能使用Amazon CloudFront工具)并且我认为实例启动时间将是一个因素。我注意到新的EC2实例可能需要5到20分钟才能启动,所以当你的负载增加时,你不能立即增加容量;看起来你需要一个或多个空闲实例来运行并准备好增加负载。

#3


Late addition:

Consider SimpleDB as well... this would eliminate the DB scaling side.

考虑使用SimpleDB ......这将消除数据库扩展方面。

For autoscaling, we rolled our own scripts to monitor, launch, and provision servers and yes, the whole process takes about 7 minutes. We do a little predictive analysis to guess when new servers will be needed and then just break them down if they aren't. Total cost: ~10 cents.

对于自动扩展,我们使用自己的脚本来监视,启动和配置服务器,是的,整个过程大约需要7分钟。我们做一些预测分析来猜测何时需要新的服务器然后如果不需要则将它们分解。总费用:约10美分。

Also, Scalr looks promising as a commercial solution (haven't used it).

此外,Scalr看起来很有希望作为商业解决方案(尚未使用它)。

Chad


分享到: