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-184.108.40.206-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”
In your scenario, we have two nodes and one cluster management server, suppose our cluster management server goes down due to any XYZ reason then what we will do? In this case, it’s not a high availability system.
Does the cluster run as a background application?
If I wanted to play solitare on an individual machine would it run on the cluster or as an app on one of the host machines?
Good Article. Is it possible to use one cluster manager box to mange two clusters?
I’ve never tried. But cannot be impossible. I’ll keep you posted if I come across such scenario.
I have a doubt that can we create shared storage through ISCSI disk service. if yes can you tell me how to setup the ISCSI disk in the rhel server?
We actually can do that but a little bit of different approach on that. Will try to provide an article on that.
I have many issues with dependencies in RHEL 6 like mod_cluster any many other like ricci not found I have to do manually with rpm -ivh which causes many issues instead of on yum. It’s a very good article, but more explanation required like fencing and iscsi creation etc..
I will try doing a separate one regarding fencing and iscsi. Till then hope following will help you.
We have an SGI cluster .SUSE 11 installed on it. from few days on master node only cd and echo commands are working. data is their on cluster.
so it is OS crash problem or something else.
I believe either the node is in read-only mode. Or some commands are removed from the server. The information you provided is not sufficient for a detailed answer.
how we can remove read only mode?????
Depending on the error messages, you could decide it is still safe to use file-system and return it read-write condition with mount -o remount,rw
It’s a bit hard to give resolutions to issue without looking at them.
I believe the servers are started up in read-only mood. Can you or your sys Admins check that? Better to back up your data and resolve the issue in the cluster soon to avoid a data loss.
It seems an issue in the OS. Looks like the server is running on read-only mode.
Thanks a lot for sharing your knowledge to us. I have learnt real experience about cluster. Have one more query, is it possible to implement cluster in all RHEL versions. (RHEL5/6/7)?
Thanx Ramesh. Yes you can do it in RHEL. But the articles I provided are more relevant to RHEL 6 because RHEL has depricated some packages in RHEL 7 and also RHEL 5 is outdated now