Pure Load Balancer runs in userland, but relies on an asynchronous non forking/non threaded/non blocking architecture. Thanks to Niels Provos' excellent event library, it can also efficiently use the kernel notification mechanisms to never waste CPU time
You MUST have a third server as a managment node but this can be shut down after the cluster starts. Also note that I do not recommend shutting down the managment server (see the extra notes at the bottom of this document for more information). You can no
In this first of five articles, learn what it means for software to be highly available and how to install and set up heartbeat software from the High-Availability Linux project on a two-node system. You'll also learn how to configure the Apache Web serve
You may know about the MySQL Cluster, which is a complex architecture to achieve high availability and performance. One of the advantages of MySQL Cluster is that each node is a peer to the others, whereas in a normal replicating system you have a master
The Linux Virtual Server is a highly scalable and highly available server built on a cluster of real servers, with the load balancer running on the Linux operating system. The architecture of the server cluster is fully transparent to end users, and the u
Fast Replication With Low Network Demand LifeKeeper Data Replication replicates data at the block level, below the file system. Most importantly, LifeKeeper Data Replication only replicates changes in data and thereby minimizes the demand on systems and n
A LAMP cluster is not the Beowulf kind of cluster that uses specialized message-passing software to tackle a computation-intensive task. It does not cover high availability features, such as automatic failover. Rather, it is a load-sharing cluster that di
One way to overcome the limits of the monolithic server is to distribute the load across many machines. By adding a second (or third) server to the available pool of machines, you can not only increase performance but also add to the stability of the netw
Edit /etc/syslog.conf to include a local1 (for example) facility entry for MasterMySQL to write to. Also update the top line so that local1 doesn't write to /var/log/messages: *.info;local1.none;mail.none;authpriv.none;cron.none /var/log/messa