Tag Info

Hot answers tagged

4

To achieve this, change the frontend stanza to the following: frontend front x.x.x.x:80 default_backend balancing acl srv1 srv_id 1 acl srv2 srv_id 2 rspadd X-Servedby:\ srv1 if srv1 rspadd X-Servedby:\ srv2 if srv2 However, a better scaling alternative would be to use cookie in the backend stanza: backend balancing cookie SRVNAME ...


3

Your answer marked YES is correct: in a load-balanced scenario, if one of the balanced servers goes down the balancer will stop sending requests to it, and pass them to other balanced pool servers instead. The benefit of a simple failover cluster is for services that cannot easily be provided in a distributed manner but which you would really like not to ...


2

It's not IP as in IP address, but IP as in instruction pointer. You've encountered a bug in nginx. Consider upgrading, if you are running an outdated version. You could also file a bug report if you can tell what happened immediately before the segfault (check the rest of the log) or have a coredump (as long as there is nothing confidential on the ...


2

I think most, important in scaling image serving is having caching in front. It can be Varnish or some CDN service. If cached well, backend is not so important for small size project. It can be a database quite well. While it has some overhead compared to static files, it may provide some basic scalability solutions like replication to multiple databases and ...


1

If you use mod_proxy in Apache 2.2 you have limited configuration options, but Apache will detect unresponsive balancerMembers and distribute requests to any remaining balancerMembers. Apache 2.4 has already some more options, but for more advanced options you're typically better off with more specialized load balancer software. After your comments: It ...


1

If your web site has only static content, Cloudflare's load balancing is enough. However, if your website has any dynamic content, which is served always by your servers, you need your own load balancing solution to distribute the requests to your own backend servers.


1

We should use srv_id which provides id value defined for server frontend front x.x.x.x:80 acl serve_us1 url_beg /west acl serve_us2 url_beg /east #defining acl for srv_id acl served_by_us1 srv_id 1 #look at srv_id acl served_by_us2 srv_id 2 #look at srv_id use_backend us1 if serve_us1 use_backend us2 if serve_us2 default_backend ...


1

When you try to access via ELB, do you get any access log or any kind of logging on your application ? If not, thats more likely a IP transition issue between ELB and EC2 instances. Could be application specific, like; do you need a real IP address of the client (like X-Forwarded-For header) ? Maybe, its because of the authentication logic that you use in ...


1

Well as you observed, you get no failover if you put all your ColdFusion eggs in the same server basket. So if that's part of your goal, clustering multiple ColdFusion instances within one box is not going to help you. However there's still merit of sorts in having multiple CF instances serving the same app on one box: one gets multiple JVMs servicing ...


1

The Admin console doesn't need to use the Apache LB layer. You can add a DNS entry for one Apache instance for the URL, and then use this to load balance to available nodes. More common for production situations is to use a LB such as F5 or software based LB that communicates to the Apache layer, the Apache nodes can then proxy to the application server ...



Only top voted, non community-wiki answers of a minimum length are eligible