【Pen of Load Balancer】

Pen is a load balancer that supports UDP and TCP base protocols such as HTTP and SMTP, allows multiple servers to appear as one externally, and can automatically detect distributed clients on available servers and stopped servers. Pen provides high availability, high performance features.

The load algorithm will continue to track clients and will also try to send the server the last time they accessed it. The client table has a large number of slots (2048 by default, can be set via command line arguments). When the table is full, the currently least used one will be thrown out and replaced with a new one.

This is a simple prioritized round robin algorithm that sends clients to different servers repeatedly.

When the Pen detects that a server is unavailable, it scans to start other servers, thus avoiding load balancing and "smoothing" failures.

 

 

This is pen, a load balancer for udp and tcp based protocols such as dns, http or smtp. It allows several servers to appear as one to the outside and automatically detects servers that are down and distributes clients among the available servers. This gives high availability and scalable performance.

 

The load balancing algorithm keeps track of clients and will try to send them back to the server they visited the last time. The client table has a number of slots (default 2048, settable through command-line arguments). When the table is full, the least recently used one will be thrown out to make room for the new one.

 

This is superior to a simple round-robin algorithm, which sends a client that connects repeatedly to different servers. Doing so breaks applications that maintain state between connections in the server, including most modern web applications.

 

 

Pen is a simple load balancer that supports the underlying protocols TCP such as HTTP or SMTP. It allows multiple servers to appear on one external and auto-detected server to reduce overhead between existing servers and clients. This enables high availability and scalable performance.

The load balancing algorithm keeps track of clients and tries to send them back to the server where they last visited . The client table has a number of slots (2048 by default, set via command line arguments). When the table is full, the most recently used ones are disposed of to make room for new ones.

This is a simple advantage round robin algorithm that sends out a client connection to a different server repeatedly. While doing so, rest, applications, and servers that maintain connections between state, including state-of-the-art web applications.

When the Pen detects that a server is unavailable, it scans for the most recently used one after that server. This way we get load balancing and "fair" failures for free.

 

 

When pen detects that a server is unavailable, it scans for another starting with the server after the most recently used one. That way we get load balancing and "fair" failover for free.

 

Correctly configured, pen can ensure that a server farm is always available, even when individual servers are brought down for maintenance or reconfiguration. The final single point of failure, pen itself,can be eliminated by running pen on several servers, using vrrp to decide which is active.

 

 

A side-effect of load-balancing web servers is that several logfiles are produced, and by default, Pen operates in a proxy mode that makes all accesses seem to come from the load balancer.The program penlogd solves this problem by merging pen's log file with the ones produced by the web servers. See penlogd(1) and penlog for details.

 

The Direct Server Return and Transparent Reverse Proxy modes make accesses seem to come directly from the client. Multiple logfiles are still created, and Penlogd can still be used to consolidate them automatically.

 

 

This load balancer is known to work on FreeBSD, Linux, HP-UX and Solaris.Other Unixes should work as well, possibly requiring trivial changes.Success stories or problem reports are welcome.

 

 

If pen is started with the -w option, statistics are saved in html format when a USR1 signal is received. The cgi script penstats can be used to simplify this; it must be edited to reflect local conditions.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=326450061&siteId=291194637