Come on Amazon, give ELB some love
coderwall.com
Come on Amazon, give ELB some love
1–10 of 15 posts
Re: Come on Amazon, give ELB some love
#2Draining 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
#3ELB 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…
http://stackoverflow.com/questions/15789166/how-amazon-elb-w...
Re: Come on Amazon, give ELB some love
#4ELB 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
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
#5Re: Come on Amazon, give ELB some love
#6Earlier 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...
Re: Come on Amazon, give ELB some love
#7Earlier 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.
Re: Come on Amazon, give ELB some love
#8https://forums.aws.amazon.com/thread.jspa?threadID=61278&sta...
^-- BenF@AWS commented on June 10th saying that amazon is now actively working on it!
Re: Come on Amazon, give ELB some love
#9Earlier 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.
Re: Come on Amazon, give ELB some love
#10In 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.