Crossroads Load Balancer 2.05 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Crossroads Load Balancer 2.05 (Default branch)
# 1  
Old 08-16-2008
Crossroads Load Balancer 2.05 (Default branch)

Image Crossroads is a daemon running in user space, and features extensive configurability, polling of back ends using wake up calls, status reporting, many algorithms to select the 'right' back end for a request (and user-defined algorithms for very special cases), and much more. Crossroads is service-independent: it is usable for any TCP service, such as HTTP(S), SSH, SMTP, and database connections. In the case of HTTP balancing, Crossroads can provide session stickiness for back end processes that need sessions, but aren't session-aware of other back ends. Crossroads can be run as a stand-alone daemon or via inetd. License: GNU General Public License v3 Changes:
This release introduces dispatch algorithms by client IP (hashed or direct) and a flag to avoid "lingering" sockets. A portability issue for 64-bit Linux has been solved.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
fair(7) 					       BSD Miscellaneous Information Manual						   fair(7)

NAME
fair -- simple TCP load balancing service DESCRIPTION
fair is a load balancer for TCP connections. It can be used to distribute incoming connections for SMTP, HTTP or any other TCP service to multiple hosts, distributing the load as evenly as possible. fair consists of two daemons. The carrousel is the front-end; it keeps track of back-end hosts and their status, and forwards incoming con- nections to the back-ends in such a way that the load is distributed fairly. The transponder runs on the back-end hosts, it registers with the carrousel and sends it status information. The TCP connections forwarded by the carrousel are not sent to the transponder daemons but are sent directly to the desired service running on the back-end host. Both daemons share a single configuration file. EXAMPLES
The following example shows how to set up fair to service HTTP connections and to distribute them over back-ends in the 192.168.1.0/24 sub- net. The configuration file /etc/fair.conf contains the following: WorkerService = http BalancerService = http AllowUDP = ^192.168.1.[0-9]+$ On www.example.com, the front-end server receiving the incoming HTTP connections, just run: carrousel On each of the back-ends run: transponder www.example.com SEE ALSO
carrousel(8), transponder(8), fair.conf(5) Debian GNU/Linux June 1, 2019 Debian GNU/Linux