I would first start ABing your setup (apache bench). - With that you might be able to adjust your instance thresholds because it could be possible that your instances can't handle the load or balance it correctly. - It's also possible the DNS server can't handle the load
As a side note, I would prevent direct IP access of the end machine by using a different port. Not sure you can do that with ELB but something to consider as it will prevent wide open direct access (bypassing your load balancer). Forcing hostname resolution helps too. If you use the public DNS name i.e ec2-some-ugly-address-112- xxxx.amazonaws.com (as EIPs are not allowed yet, i think) you should have nothing to worry about. On Dec 28 2009, 5:02 pm, "Damon P. Cortesi" <[email protected]> wrote: > Hi, > > Ever since I set up my farm with Amazon's Elastic Load Balancer, I've > had reports from scattered people that they can no longer access my > site (tweetstats.com). I have yet to track this down, primarily > because I can't debug the issue as it seems to be somewhat random. > Reports indicate that the site just times out when they try to access > it via DNS. Accessing via IP address of the www-app role works > perfectly fine, though. > > The /only/ thing I can think of at this point is that my ELB resolves > to 174.129.202.0 and some networks can't route to this address, for > whatever reason. I'd like to try to set up a different ELB, but I'm > not quite sure how to do this. If I remove the current one from the > Server Farms -> ELB page, does it automatically create a new one? Even > on the role config page, I can't add another port as the fields for > load balancer and instance port are disabled. > > Thanks for any help, > > Damon
-- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en.
