| Federico, 503 would be due to a node being not responsive, you can configure your cluster to disable a node after one or more failures with mod_cluster. now back to mod_proxy_balancer and mod_proxy, if i understand correctly, you have a scenario where you have one or more contexts served by all of the nodes in the cluster, and another context served only by some nodes, i.e.: Node1 => /foo,/bar Node2 => /foo Node3 => /foo,/bar you want /foo to be served by all of the nodes, and /bar just by Node1, and have Node3 as a hot standby (failover), if that is the case, you would probably need multiple load balancers defined with two different location blocks, so something like this: <proxy balancer://foocluster> BalancerMember http://node1:8080 BalancerMember http://node2:8080 BalancerMember http://node3:8080 </proxy> <proxy balancer://barcluster> BalancerMember http://node1:8080 # the hot standby on node3 BalancerMember http://node3:8080 status=+H </proxy> <location /foo> ProxyPass balancer://foocluster ProxyPassReverse http://node1:8080 ProxyPassReverse http://node2:8080 ProxyPassReverse http://node3:8080 </location> <location /bar> ProxyPass balancer://barcluster ProxyPassReverse http://node1:8080 ProxyPassReverse http://node3:8080 </location> -Roman On Jul 3, 2014, at 10:48 AM, Jeff Trawick <trawick@xxxxxxxxx> wrote:
|
|