Load balancing
From Resin 3.0
(Difference between revisions)
m (Load Balancing Configuration moved to Load balancing) |
|||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Category:Configuration]] [[Category:Cluster]] | + | {{Cleanup}} [[Category:Configuration]] [[Category:Cluster]] |
| − | + | Resin documentation is at http://www.caucho.com/resin/doc/balance.xtp | |
| − | Resin documentation is at http://www.caucho.com/resin | + | |
Load balancing spreads the load among multiple backend Resin servers in a [[cluster|Cluster]]. A frontend Resin server proxies requests to the backend servers and sends the results to the clients. | Load balancing spreads the load among multiple backend Resin servers in a [[cluster|Cluster]]. A frontend Resin server proxies requests to the backend servers and sends the results to the clients. | ||
| Line 15: | Line 14: | ||
# pools the proxy sockets for efficiency | # pools the proxy sockets for efficiency | ||
| − | == The Backend [[cluster|Cluster]] | + | == The Backend [[cluster|Cluster]] == |
# does the actual work: the database querying and form processing | # does the actual work: the database querying and form processing | ||
# manages persistent sessions | # manages persistent sessions | ||
| − | == | + | == resin.xml == |
The frontend needs to configure: | The frontend needs to configure: | ||
| Line 27: | Line 26: | ||
# A LoadBalanceServlet to dispatch requests to the backend | # A LoadBalanceServlet to dispatch requests to the backend | ||
| − | ==== | + | ==== resin.xml ==== |
<resin xmlns="http://caucho.com/ns/resin" | <resin xmlns="http://caucho.com/ns/resin" | ||
xmlns:resin="http://caucho.com/ns/resin/core"> | xmlns:resin="http://caucho.com/ns/resin/core"> | ||
| − | <server> | + | <cluster id="load-balance"> |
| − | + | <server-default> | |
| + | <http host="*" port="80"/> | ||
| + | </server-default> | ||
| − | + | <server id="web-a" address="192.168.0.10" port="6800"/> | |
| − | + | ||
| − | < | + | <host id=""> |
| − | + | <web-app id=""> | |
| − | + | <rewrite-dispatch> | |
| + | <load-balance regexp="" cluster="app-tier"/> | ||
| + | </rewrite-dispatch> | ||
| + | </web-app> | ||
| + | </host> | ||
| + | </cluster> | ||
| − | < | + | <cluster id="app-tier"> |
| + | <root-directory>/var/www/</root-directory> | ||
| − | + | <server id="app-a" address="192.168.0.20" port="6800"/> | |
| − | + | <server id="app-b" address="192.168.0.21" port="6800"/> | |
| − | + | <server id="app-c" address="192.168.0.22" port="6800"/> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | <host id=""> | |
| − | + | <web-app-deploy path="webapps"/> | |
| − | + | </host> | |
| − | + | </cluster> | |
| − | + | </resin> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 18:27, 1 December 2011
|
This article requires cleanup and may refer to a legacy version of Resin.
Please visit http://www.caucho.com/documentation/ for the most up-to-date documentation. |
Resin documentation is at http://www.caucho.com/resin/doc/balance.xtp
Load balancing spreads the load among multiple backend Resin servers in a Cluster. A frontend Resin server proxies requests to the backend servers and sends the results to the clients.
We'll use 192.168.0.10 as the frontend machine and 192.168.0.20 through 192.168.0.28 as the backend machines.
The frontend server and the backend cluster have different configurations since they perform different roles.
Contents |
The Frontend Server
- dispatches requests to the backend servers, generally using sticky sessions
- acts as a Proxy Cache for the backend cluster
- pools the proxy sockets for efficiency
The Backend Cluster
- does the actual work: the database querying and form processing
- manages persistent sessions
resin.xml
The frontend needs to configure:
- The external HTTP and HTTPS ports its listening to
- The cluster-definition of the backend cluster
- A LoadBalanceServlet to dispatch requests to the backend
resin.xml
<resin xmlns="http://caucho.com/ns/resin" xmlns:resin="http://caucho.com/ns/resin/core"> <cluster id="load-balance"> <server-default> <http host="*" port="80"/> </server-default> <server id="web-a" address="192.168.0.10" port="6800"/> <host id=""> <web-app id=""> <rewrite-dispatch> <load-balance regexp="" cluster="app-tier"/> </rewrite-dispatch> </web-app> </host> </cluster> <cluster id="app-tier"> <root-directory>/var/www/</root-directory> <server id="app-a" address="192.168.0.20" port="6800"/> <server id="app-b" address="192.168.0.21" port="6800"/> <server id="app-c" address="192.168.0.22" port="6800"/> <host id=""> <web-app-deploy path="webapps"/> </host> </cluster> </resin>
