Live data from Hacker News

Come on Amazon, give ELB some love

coderwall.com

1–10 of 15 posts

Re: Come on Amazon, give ELB some love

#2
ELB already does weighting, directing requests depending instance type and instance load. Can't find where in the docs this is clarified unfortunately. Have witnessed this with my own eyes though!

Draining is a huge issue for us. Investigating ways to add a secondary layer of balancing behind ELB to help mitigate it, which is completely silly. We shouldn't need to do this. ELB should have supported gracefully terminating connections from Day 1, IMO. Last I heard it was being 'considered'.

Re: Come on Amazon, give ELB some love

#3
post #2

ELB already does weighting, directing requests depending instance type and instance load. Can't find where in the docs this is clarified unfortunately. Have witnessed this with my own eyes though! Draining is a huge issue for us. Investigating ways to add a secondary layer of balancing behind ELB to help mitigate it, which is completely silly. We shouldn't need to do this. ELB should have supported gracefully termina…

Docs talk about Availability Zones, but there is zero mention of weighting -- either that it's done, or that it's not done. This is a very strange omission. Googling reveals that balancing is done by counting outstanding requests to each instance:

http://stackoverflow.com/questions/15789166/how-amazon-elb-w...

https://forums.aws.amazon.com/message.jspa?messageID=146233

Re: Come on Amazon, give ELB some love

#4
post #2

ELB already does weighting, directing requests depending instance type and instance load. Can't find where in the docs this is clarified unfortunately. Have witnessed this with my own eyes though! Draining is a huge issue for us. Investigating ways to add a secondary layer of balancing behind ELB to help mitigate it, which is completely silly. We shouldn't need to do this. ELB should have supported gracefully termina…

Docs talk about Availability Zones, but there is zero mention of weighting -- either that it's done, or that it's not done. This is a very strange omission. Googling reveals that balancing is done by counting outstanding requests to each instance: http://stackoverflow.com/questions/15789166/how-amazon-elb-w... https://forums.aws.amazon.com/message.jspa?messageID=146233

> But there is zero mention of weighting

It is called WRR (Weighted Round Robin). Here are some docs to get you started:

http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/Wei...

Re: Come on Amazon, give ELB some love

#5
They have been - and they successfully nerfed half a dozen of ours (public facing) when they did the migration about three weeks back. Most recent upgrade added the ability for R53 to do latency based and healthcheck based DNS (with ELBs, that is), which is pretty shiny. As others have noted, it already auto-weights.

Re: Come on Amazon, give ELB some love

#6
post #4

Earlier quoted context omitted.

Docs talk about Availability Zones, but there is zero mention of weighting -- either that it's done, or that it's not done. This is a very strange omission. Googling reveals that balancing is done by counting outstanding requests to each instance: http://stackoverflow.com/questions/15789166/how-amazon-elb-w... https://forums.aws.amazon.com/message.jspa?messageID=146233

> But there is zero mention of weighting It is called WRR (Weighted Round Robin). Here are some docs to get you started: http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/Wei...

That's for Route 53 (DNS). The subject here is ELB, a different AWS technology.

Re: Come on Amazon, give ELB some love

#7
post #4

Earlier quoted context omitted.

> But there is zero mention of weighting It is called WRR (Weighted Round Robin). Here are some docs to get you started: http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/Wei...

That's for Route 53 (DNS). The subject here is ELB, a different AWS technology.

Yes, indeed! My thinking was that you could use this Route 53 feature to route traffic across several ELBs to accomplish the desired effect.

Re: Come on Amazon, give ELB some love

#9
post #7

Earlier quoted context omitted.

That's for Route 53 (DNS). The subject here is ELB, a different AWS technology.

Yes, indeed! My thinking was that you could use this Route 53 feature to route traffic across several ELBs to accomplish the desired effect.

Yes, sounds like a good idea (if you have control of the DNS)

Re: Come on Amazon, give ELB some love

#10
How about more control over the software & configuration side of ELB as well? If you could control more things that nginx or haproxy let you control, I think there would be a lot less need for another routing mechanism behind ELB.

In addition to weighting, we need an nginx layer for different app pools, custom routing options, max connections limits, request queueing, url rewriting, static content serving for specific requests. The list goes on but these things could easily be brought up into the ELB layer.

Post reply on HN