Hi all, this time I decided to share my knowledge about Linux clustering with you as a series of guides titled “Linux Clustering For a Failover Scenario“.
Following are the 4-article series about Clustering in Linux:
First of all, you will need to know what clustering is, how it is used in industry and what kind of advantages and drawbacks it has etc.
What is Clustering
Clustering is establishing connectivity among two or more servers in order to make it work like one. Clustering is a very popular technic among Sys-Engineers that they can cluster servers as a failover system, a load balance system or a parallel processing unit.
By this series of guide, I hope to guide you to create a Linux cluster with two nodes on RedHat/CentOS for a failover scenario.
Since now you have a basic idea of what clustering is, let’s find out what it means when it comes to failover clustering. A failover cluster is a set of servers that works together to maintain the high availability of applications and services.
For an example, if a server fails at some point, another node (server) will take over the load and gives end user no experience of down time. For this kind of scenario, we need at least 2 or 3 servers to make the proper configurations.
I prefer we use 3 servers; one server as the red hat cluster enabled server and others as nodes (back end servers). Let’s look at below diagram for better understanding.
Cluster Server: 172.16.1.250 Hostname: clserver.test.net node01: 172.16.1.222 Hostname: nd01server.test.net node02: 172.16.1.223 Hostname: nd02server.test.net
In above scenario, cluster management is done by a separate server and it handles two nodes as shown by the diagram. Cluster management server constantly sends heartbeat signals to both nodes to check whether if anyone is failing. If anyone has failed, the other node takes over the load.
Advantages of Clustering Servers
- Clustering servers is completely a scalable solution. You can add resources to the cluster afterwards.
- If a server in the cluster needs any maintenance, you can do it by stopping it while handing the load over to other servers.
- Among high availability options, clustering takes a special place since it is reliable and easy to configure. In case of a server is having a problem providing the services furthermore, other servers in the cluster can take the load.
Disadvantages of Clustering Servers
- Cost is high. Since the cluster needs good hardware and a design, it will be costly comparing to a non-clustered server management design. Being not cost effective is a main disadvantage of this particular design.
- Since clustering needs more servers and hardware to establish one, monitoring and maintenance is hard. Thus increase the infrastructure.
Now let’s see what kind of packages/installations we need to configure this setup successfully. The following packages/RPMs can be downloaded by rpmfind.net.
- Ricci (ricci-0.16.2-75.el6.x86_64.rpm)
- Luci (luci-0.26.0-63.el6.centos.x86_64.rpm)
- Mod_cluster (modcluster-0.16.2-29.el6.x86_64.rpm)
- CCS (ccs-0.16.2-75.el6_6.2.x86_64.rpm)
- Clusterlib (clusterlib-18.104.22.168-68.el6.x86_64.rpm)
Let’s see what each installation does for us and their meanings.
- Ricci is a daemon which used for cluster management and configurations. It distributes/dispatches receiving messages to the nodes configured.
- Luci is a server that runs on the cluster management server and communicates with other multiple nodes. It provides a web interface to make things easier.
- Mod_cluster is a load balancer utility based on httpd services and here it is used to communicate the incoming requests with the underlying nodes.
- CCS is used to create and modify the cluster configuration on remote nodes through ricci. It is also used to start and stop the cluster services.
- CMAN is one of the primary utilities other than ricci and luci for this particular setup, since this acts as the cluster manager. Actually, cman stands for CLUSTER MANAGER. It is a high-availability add-on for RedHat which is distributed among the nodes in the cluster.
Read the article, understand the scenario we’re going to create the solution to, and set the pre-requisites for the implementation. Let’s meet with the Part 2, in our upcoming article, where we learn How to install and create the cluster for the given scenario.
Keep connected with Tecmint for handy and latest How To’s. Stay Tuned up for the part 02 (Linux Servers clustering with 2 Nodes for a failover scenario on RedHAT/CentOS – Creating the cluster) soon.
36 thoughts on “Introduction and Advantages/Disadvantages of Clustering in Linux – Part 1”
I have two question 1)for connecting two nodes together and them to server, do you use hub? or lan?
2) this method test on which version linux x86_64? centos 7? or ?
I used LAN and RHEL 6.x
Hello, Thanks for the tutorial. Am wondering if these packages are available for debian-based distros such as Ubuntu too?
cman you can use. But i dont think ricci, luci and other packs are available. You may use corosync, pacemaker, pcs etc. on ubuntu
Hi Thilina, what´s about haproxy?
HA proxy is also a reputed tool for the same purpose. And is used by many industrial giants. You can expect an article for HA in near future.
Hi Ravi, I couldn’t find the clustering rpm packages(ricci, luci, ccs, CMAN, cluster lib) to download, can you please give me the exact path for it, so that i would be helpfull
You can try following URL.
Wow! This is really good material, nicely and explained using simple language. As a newbie, I have found it helpful, thanks for sharing such helpful information, really inspiring, a big up to you.
Thank you Givious ! ! ! !
When you are going to publish Part 4: Syncing the Configurations and Starting Up the Clustering
I have completed all 3 parts
Great. I will post the last part soon. Sorry for the delay
Hi, first, I want to congratulate you for your website and excellent tutorials!! Great job and thanks for sharing your knowledge.. My doubt is about the Cluster Management Server, what if it fails? Is there a solution within the clustering system, or it is necessary to implement a contingency plan?
Thanks in advantage!
Thank you for your interest for the post. For the question you ask, It is necessary to implement a contingency plan if you have critical and important data in the cluster. You can setup a fail-over for the cluster management server and services. But this way, it will cause additional costs for the resources. I will share with you if I could find a different and more convenient solution regarding this.
For two different geographical DC location, you may prefer GRID computing.
I am eagerly waiting for your next article. Please make it hurry if you can. Thanks.
Thanx for your interest. Will post it ASAP.
Part 2 and part 3 are already posted. Will post part 4 soon.
There is another big disadvantage in rhel cluster that we are facing everyday in our environment. That is red hat officially does not support extended distance (xd or stage) cluster,that located on two different geographical DC location. Even no solution for this.
Thanx for sharing your knowledge :)