Red Hat RHCS kit installation and configuration

The three core functions provided by RHCS high-availability clusters are the core functions of RHCS. When an application fails or the system hardware or network fails, the application can automatically and quickly switch from one node to another through the high availability service management component provided by RHCS, the node failover function is transparent to the client to ensure continuous and uninterrupted service provision by applications. This is the function implemented by the RHCS high-availability cluster. RHCS uses LVS (LinuxVirtualServer) to provide Load Balancing

Three core functions provided by RHCS

High-availability clusters are the core functions of RHCS. When an application fails or the system hardware or network fails, the application can automatically and quickly switch from one node to another through the high availability service management component provided by RHCS, the node failover function is transparent to the client to ensure continuous and uninterrupted service provision by applications. This is the function implemented by the RHCS high-availability cluster.

RHCS provides Server Load balancer clusters through LVS (LinuxVirtualServer). LVS is an open-source and powerful IP-based Server Load balancer technology. LVS consists of Server Load balancer and service access nodes, through the load scheduling function of LVS, client requests can be evenly distributed to each service node, and multiple load allocation policies can also be defined. When a request comes in, the cluster system determines the service node to which the request should be distributed based on the scheduling algorithm, and then responds to the client request from the allocated node. At the same time, LVS also provides the service node failover function, when a service node cannot provide services, LVS automatically blocks the faulty node and removes the failed node from the cluster, at the same time, the new node requests are smoothly transferred to other normal nodes. When the faulty node returns to normal, LVS automatically adds the node to the cluster. This series of switching actions are transparent to users. The failover function ensures uninterrupted and stable service operation.

RHCS provides the storage cluster function through the GFS file system. GFS is short for GlobalFileSystem. It allows multiple services to read and write a single shared file system at the same time, by placing shared data in a shared file system, a storage cluster eliminates the trouble of synchronizing data between applications. GFS is a distributed file system that uses the lock management mechanism, to coordinate and manage the read and write operations of multiple service nodes on the same file system. Currently, the most common version is gfs2, And the GFS file system must run on the cluster.

RHCS + GFS (Red Hat HA + GFS) http://www.linuxidc.com/Linux/2014-04/99574.htm

Web Service shared storage cluster architecture http://www.linuxidc.com/Linux/2013-05/84888.htm Based on RHCS + iSCSI + CLVM

RHCS multi-node deployment application enterprise environment http://www.linuxidc.com/Linux/2013-05/84456.htm

RedHat 5.8x64 RHCS Oracle 10gR2 HA practice configuration http://www.linuxidc.com/Linux/2013-03/81589.htm

Java-based HA dual-machine Hot Standby http://www.linuxidc.com/Linux/2012-12/76587.htm of RHCS

Diagram of RHCS installation configuration and application http://www.linuxidc.com/Linux/2012-11/75111.htm

Composition of RHCS Clusters

RHCS is a collection of cluster tools, mainly composed of the following parts:

1. cluster architecture Manager

This is a basic suite of RHCS clusters. It provides the basic functions of a cluster to make each node work together, including the distributed Cluster Manager (CMAN), member relationship management, lock management (DLM), configuration file management (CCS), and gate device (FENCE ).

2. high-availability Service Manager

Provides node service monitoring and service failover. When a node service fails, the service is transferred to another healthy node.

3. cluster configuration management tools

The latest version of RHCS uses LUCI to configure and manage RHCS clusters. LUCI is a web-based cluster configuration method. with luci, you can easily build a powerful cluster system. The node host can use ricci to communicate with the luci Management Terminal.

4. LinuxVirtualServer

LVS is an open-source Server Load balancer software. LVS can distribute client requests to various service nodes based on specified load policies and algorithms to achieve dynamic and intelligent load balancing.

In addition to the core components above, the RHCS cluster function can be supplemented by the following components.

5. RedHatGFS (GlobalFileSystem)

GFS is a cluster file system developed by Redhat. The latest version is GFS2. The GFS file system allows multiple services to read and write a disk partition at the same time. GFS enables centralized data management, this eliminates the trouble of Data Synchronization and copying, but GFS cannot be isolated. Installing GFS requires the support of the underlying components of RHCS.

6. ClusterLogicalVolumeManager

Cluster logical volume management, that is, CLVM, is an extension of LVM, which allows machines in the cluster to use LVM to manage shared storage.

7. iSCSI

ISCSI is a standard for data block transmission over the Internet Protocol, especially over Ethernet. It is a new storage technology based on the IPStorage theory, RHCS can use ISCSI technology to export and allocate shared storage.

RHCS Cluster Structure

Is a typical RHCS cluster topology: The entire topology is divided into three layers

The top layer is the LVS Load Balancing layer, the middle layer is the RealServer layer, which is the service node part, and the last layer is the shared storage layer, which is mainly used to provide shared storage space for the GFS file system.

RHCS cluster operating principles and functions

1. Distributed Cluster Manager (CMAN)

ClusterManager (CMAN) is a distributed cluster management tool that runs on each node of the cluster and provides cluster management tasks for RHCS.

CMAN is used to manage cluster members, messages, and notifications. It monitors the running status of each node to understand the relationship between node members. When a node in the cluster fails, the node member relationship will change, and CMAN promptly notifies the underlying layer of this change, and then make corresponding adjustments.

2. Lock Management (DLM)

DistributedLockManager (DLM) is a distributed lock manager. It is an underlying component of RHCS and provides a common lock operation mechanism for the cluster. In the RHCS cluster system, DLM runs on each node in the cluster. GFS uses the lock mechanism of the lock manager to synchronize access to the file system metadata. CLVM synchronously updates data to LVM volumes and volume groups through the lock manager.

DLM does not need to set the lock management server. It adopts the peering lock management method, which greatly improves the processing performance. At the same time, DLM avoids the performance bottleneck of overall recovery when a single node fails. In addition, DLM requests are local and do not require network requests, so the requests take effect immediately. Finally, the DLM uses a layered mechanism to implement parallel lock modes for multiple lock spaces.

3. Configuration File Management (CCS)

CCS terconfigurationsystem (CCS) is mainly used for managing cluster configuration files and synchronizing configuration files between nodes. Sometimes, the luci management interface may become necessary because the network and other aspects are not so smooth. CCS runs on each node of the cluster and monitors a single configuration file/etc/cluster on each cluster node. conf status. When this file changes, it is updated to every node in the cluster, and the configuration file of each node is synchronized at all times. For example, the administrator updates the cluster configuration file on node A. After CCS finds that the configuration file of node A has changed, the change will be immediately transmitted to other nodes.

The rhcs configuration file is cluster. conf, which is an xml file containing the cluster name, cluster node information, cluster resources and service information, and fence devices.

4. Gate device (FENCE)

FENCE devices are an essential part of the RHCS cluster. FENCE devices can be used to avoid split-brain problems caused by unpredictable situations and FENCE devices, to solve these problems, Fence devices directly issue hardware management commands to servers or storage through the hardware management interfaces of servers or storage, or external power management devices, restart or shut down the server, or disconnect from the network.

FENCE works in the following way: when a host is abnormal or down due to an accident, the Standby opportunity first calls the FENCE device, and then restarts or isolates the abnormal host from the network through the FENCE device, after the FENCE operation is successfully executed, the information is returned to the slave machine. After receiving the successful information of FENCE, the slave machine starts to take over the services and resources of the host. In this way, resources occupied by abnormal nodes are released through the FENCE device, ensuring that resources and services always run on one node.

Rhcs fence devices can be divided into two types: Internal FENCE and external FENCE. Common internal FENCE devices include IBMRSAII cards, HP iLO cards, and IPMI devices, external fence devices include UPS, SANSWITCH, and NETWORKSWITCH.

5. high-availability Service Manager

High Availability service management is mainly used to supervise, start, and stop cluster applications, services, and resources. It provides a management capability for cluster services. When a node fails, the high availability cluster service management process can transfer services from this failed node to other healthy nodes, in addition, this service transfer capability is automatic and transparent.

RHCS uses rgmanager to manage cluster services. rgmanager runs on each cluster node and the corresponding process on the server is clurgmgrd.

In a RHCS cluster, high availability services include cluster services and cluster resources. Cluster services are actually application services, such as apache and mysql. There are many cluster resources, for example, an IP address, a running script, and an ext3/GFS file system.

　　

In a RHCS cluster, the high availability service is combined with a Failover domain. A failover domain is a collection of cluster nodes that run specific services. In the failed transfer domain, you can set a priority for each node. The priority is used to determine the order of service transfer when the node fails. If no priority is specified for the node, the Cluster High Availability service will be transferred between any nodes. Therefore, by creating a failed transfer domain, you can not only set the order of service transfer between nodes, but also restrict a service to switch only within the node specified by the failed transfer domain.

6. cluster configuration management tools

Conga is a new network-based cluster configuration tool. Conga configures and manages cluster nodes through web. Conga consists of two parts: luci and ricci. luci is installed on an independent computer for cluster configuration and management. ricci is installed on each cluster node, luci communicates with each node in the cluster through ricci.

RHCS also provides some powerful cluster command line management tools, commonly used include clustat, cman_tool, ccs_tool, fence_tool, and clusvcadm. The usage of these commands will be described below.

7. RedhatGFS

GFS is a storage solution provided by RHCS for cluster systems. It allows multiple nodes in the cluster to share storage at the block level. Each node shares a storage space, GFS is a cluster file system provided by RHCS. multiple nodes mount one file system partition at a time, while the file system data is not damaged, this is not implemented by a single file system.

GFS uses the lock manager to manage I/O operations when multiple nodes perform read and write operations on a file system. When a write process operates on a file, the file is locked. At this time, other processes are not allowed to perform read/write operations. The lock is released until the write process completes normally, other read/write processes can operate on this file. In addition, when a node modifies data on the GFS file system, such modifications are immediately visible on other nodes through the underlying communication mechanism of RHCS.

When building a RHCS cluster, GFS is generally used as shared storage and runs on each node. It can be configured and managed through RHCS management tools. The relationships between RHCS and GFS need to be explained. Generally, it is easy for beginners to confuse this concept: Running RHCS, GFS is not necessary, and GFS is required only when shared storage is required, to build a GFS cluster file system, you must have the underlying support of RHCS. Therefore, you must install the RHCS component on the nodes where the GFS file system is installed.

In the next section, we will explain how to deploy and manage rhcs.

For more details, refer to the highlights on the next page.: Http://www.linuxidc.com/Linux/2014-06/102770p2.htm