{"id":1631,"date":"2013-06-21T20:16:49","date_gmt":"2013-06-21T14:31:49","guid":{"rendered":"https:\/\/www.sparksupport.com\/blog\/?p=1631"},"modified":"2024-06-24T10:36:20","modified_gmt":"2024-06-24T10:36:20","slug":"apache-load-balancing_it-infrastructuremanagement","status":"publish","type":"post","link":"https:\/\/sparksupport.com\/blog\/apache-load-balancing_it-infrastructuremanagement\/","title":{"rendered":"Apache Load Balancing"},"content":{"rendered":"

Apache Load Balancing is a technique aiming at distributing workload in a computer network<\/a>, in order to optimally utilize resources, avoid overload and maximize throughput.Computer clusters rely on load balancing to distribute workload across network links, CPUs, web servers, etc. A server farm is a common application of load balancing, where multiple servers seamlessly provide a single Internet service. In this case the load balancer accepts requests from external clients and forwards them to one of the available back-end servers according to a scheduling algorithm (e.g. round robin, random choice, on a reported load basis, etc..)Load balancers can be implemented using dedicated hardware or ad-hoc software<\/p>\n

Mod_Proxy_Balancer:-<\/span><\/p>\n

mod_proxy_balancer is an Apache module available since Apache 2.1. It allows turning an Apache installation into a load balancer retrieving requested pages from two or more back-end web servers and delivering them to the user\u2019s computer.One important feature of mod_proxy_balancer is that it can keep track of sessions which means that a single user always deals with the same back-end web server (sticky sessions).<\/p>\n

Requirements for configuring apache load balancer:<\/span><\/p>\n

The module requires:
\n1) an Apache HTTP Server installation version 2.1 or later
\n2) mod_proxy extension.<\/p>\n

Apache Installation steps for load balancing:-<\/span>
\nFirst install Apache Portable Runtime, APR Utils, and the Httpd server<\/p>\n

a)APR installation<\/p>\n

wget http:\/\/mirrors.axint.net\/apache\/\/apr\/apr-1.4.6.tar.gz
\ntar -xvzf apr-1.4.6.tar.gz
\ncd apr-1.4.6\/
\n.\/configure
\nmake
\nmake install<\/p><\/blockquote>\n

b)APR utils<\/p>\n

wget http:\/\/mirrors.axint.net\/apache\/\/apr\/apr-util-1.4.1.tar.gz
\ntar -xvzf apr-util-1.4.1.tar.gz
\ncd apr-util-1.4.1
\n.\/configure –with-apr=\/usr\/local\/apr
\nmake
\nmake install<\/p><\/blockquote>\n

c)Apache installation (version-2.2.24)<\/p>\n

Download httpd 2.2.24.tar.gz and execute the following commands<\/p>\n

tar -xvzf httpd-2.2.24.tar.gz
\ncd httpd-2.2.24
\n.\/configure –prefix=\/usr\/local\/apache2 –enable-mods-shared=all –enable-http –enable-deflate –enable-expires –enable-slotmem-shm –enable-headers –enable-rewrite –enable-proxy –enable-proxy-balancer –enable-proxy-http –enable-proxy-fcgi –enable-mime-magic –enable-log-debug
\nmake && make install<\/p><\/blockquote>\n

Apache installation which supports load balancing is now complete.<\/p>\n

Configuration changes to be made in apache:-<\/span><\/p>\n

When you configure mod_proxy_balancer, you can choose among three load-balancing algorithms: Request Counting, Weighted Traffic Counting, and Pending Request Counting. The best algorithm to use depends on the individual use case. Here I have used request counting method.<\/p>\n

Uncomment the following lines in your httpd.conf file<\/p>\n

LoadModule proxy_http_module modules\/mod_proxy_http.so
\nLoadModule proxy_module modules\/mod_proxy.so
\nLoadModule proxy_balancer_module modules\/mod_proxy_balancer.so
\nLoadModule negotiation_module modules\/mod_negotiation.so<\/p><\/blockquote>\n

Add the lines for load balancer configuration shown below to the end of httpd.conf<\/p>\n

#Distribution servers and method
\n<Proxy balancer:\/\/mybalancer>
\nBalancerMember http:\/\/192.168.1.21:80 loadfactor=1
\nBalancerMember http:\/\/192.168.1.32:80 loadfactor=3
\nProxySet lbmethod=byrequests
\n<\/Proxy>
\nProxyPass \/balance balancer:\/\/mybalancer\/
\n<\/IfModule><\/p><\/blockquote>\n

Now restart apache and enter the URL http:\/\/localhost\/balance. The page loaded will be from 192.168.1.21. Refresh page 3 times and content from 192.168.1.32 will be displayed on all 3 occasions(since load factor is 3 by request). We can use any name for Proxy balancer. It just signifies application name. Balancer Member directive specifies worker IP and port. As many balancer members as needed can be specified depending on the need. Load factor specifies load each worker takes. 2IP’s in this case. lbmethod specifies the algorithm to be used for load balancing. ProxyPass directive specifies that content from workers will be available at http:\/\/localhost\/balance<\/p>\n

Next add these lines to httpd.conf file<\/p>\n

#Load Balancer Configuration- Balancer manager for web interface
\n<IfModule mod_proxy_balancer.c>
\n<Location “\/balancer-manager”>
\nSetHandler balancer-manager
\nOrder deny,allow
\nDeny from all
\n# Allow from local subnet only
\nAllow from all
\n<\/Location><\/p><\/blockquote>\n

Occasionally you may need to change your load balancing configuration, but that may not be easy to do without affecting the running server. The above part of the configuration provides a web interface to handle the back end workers. mod_status extension is required for this feature. The balancer manager can be used to change load factor associated with a worker or to put it in offline mode. Statistics and configuration details will be displayed and settings could be edited through this interface. The Balancer Manager can be accessed by pointing a browser at http:\/\/localhost\/balancer-manager.<\/p>\n

Load Balancing Algorithms<\/span><\/p>\n

There are mainly 3 algorithms for load balancing.
\n1)Request counting :- With this algorithm, incoming requests are distributed among back-end workers in such a way that each back end gets a proportional number of requests defined in the configuration by the load-factor variable. The example shown in this case uses request counting algorithm. 1 request out of every 4 will be sent to 192.168.1.21 and 3 requests will be sent to 192.168.1.32<\/p>\n

2)Weighted Traffic Counting Algorithm :- Weighted Traffic Counting considers the number of bytes instead of number of requests.<\/p>\n

3)Pending Request Counting Algorithm :- In this algorithm, the scheduler keeps track of the number of requests that are assigned to each back-end worker at any given time. Each new incoming request will be sent to the back end that has least number of pending requests \u2013 in other words, to the back-end worker that is relatively least loaded. This helps keep the request queues even among the back-end workers, and each request generally goes to the worker that can process it the fastest.<\/p>\n

<\/div>\n