{"id":1379,"date":"2025-02-09T02:06:02","date_gmt":"2025-02-08T23:06:02","guid":{"rendered":"https:\/\/wafatech.sa\/blog\/linux\/linux-security\/configuring-high-availability-clusters-with-pacemaker-on-linux\/"},"modified":"2025-03-10T02:47:11","modified_gmt":"2025-03-09T23:47:11","slug":"configuring-high-availability-clusters-with-pacemaker-on-linux","status":"publish","type":"post","link":"https:\/\/wafatech.sa\/blog\/linux\/linux-security\/configuring-high-availability-clusters-with-pacemaker-on-linux\/","title":{"rendered":"Configuring High Availability Clusters with Pacemaker on Linux"},"content":{"rendered":"


\n<\/p>\n

High availability (HA) is a critical aspect of modern IT infrastructure, ensuring that services remain online and accessible even in the event of hardware failures or maintenance events. One of the most popular solutions for implementing HA on Linux is Pacemaker<\/strong>, a cluster resource manager that enables you to manage services and resources across multiple nodes in a way that minimizes downtime. In this article, we will walk through the steps for configuring a High Availability cluster using Pacemaker on Linux.<\/p>\n

<\/p>\n

Prerequisites<\/h2>\n

<\/p>\n

Before we begin, please ensure that you meet the following prerequisites:<\/p>\n

<\/p>\n

    <\/p>\n
  1. Linux Distributions:<\/strong> We recommend using CentOS, RHEL, or Ubuntu, but the steps can be adapted for other distributions.<\/li>\n

    <\/p>\n

  2. Multiple Nodes:<\/strong> At least two nodes (servers) that will participate in the HA cluster.<\/li>\n

    <\/p>\n

  3. Root Access:<\/strong> Administrative privileges on all nodes.<\/li>\n

    <\/p>\n

  4. Network Connectivity:<\/strong> Ensure that all nodes can communicate with each other over a private network.<\/li>\n

    <\/p>\n

  5. Package Installation:<\/strong> The necessary packages should be installed on all nodes. Pacemaker, Corosync, and related tools are required.<\/li>\n

    \n<\/ol>\n

    <\/p>\n

    You can install the necessary packages using the package manager of your distribution. For instance:<\/p>\n

    <\/p>\n

    # For CentOS\/RHEL
    \nsudo yum install pacemaker pcs corosync
    \n
    \n# For Ubuntu
    \nsudo apt-get install pacemaker corosync<\/code><\/pre>\n
    <\/p>\n
    Step 1: Enable and Start the Required Services<\/h2>\n
    <\/p>\n
    On each node, you’ll need to enable and start the following services:<\/p>\n
    <\/p>\n
    # For CentOS\/RHEL
    \nsudo systemctl enable pcsd
    \nsudo systemctl start pcsd
    \n
    \n# For Ubuntu
    \nsudo systemctl enable pacemaker
    \nsudo systemctl start pacemaker<\/code><\/pre>\n
    <\/p>\n
    Make sure you do the same for corosync<\/code>.<\/p>\n
    <\/p>\n
    Step 2: Authenticate the Nodes<\/h2>\n
    <\/p>\n
    To form a cluster, the nodes must be able to communicate with each other. On one of the nodes, set a password for the cluster:<\/p>\n
    <\/p>\n
    sudo passwd hacluster<\/code><\/pre>\n
    <\/p>\n
    Make sure to provide the same password on all participating nodes. Now, authenticate each node to the cluster:<\/p>\n
    <\/p>\n
    # On all nodes
    \nsudo pcs cluster auth <node1> <node2> -u hacluster -p <password><\/code><\/pre>\n
    <\/p>\n
    Replace <node1><\/code> and <node2><\/code> with the actual hostnames of your servers, and <password><\/code> with the password you set earlier.<\/p>\n
    <\/p>\n
    Step 3: Create the Cluster<\/h2>\n
    <\/p>\n
    Now that the nodes are authenticated, you can create the cluster. This command should be executed on one of the nodes:<\/p>\n
    <\/p>\n
    sudo pcs cluster setup --name my_cluster <node1> <node2><\/code><\/pre>\n
    <\/p>\n
    Replace my_cluster<\/code> with a name of your choosing for the cluster. You can also add additional nodes by appending them to the command.<\/p>\n
    <\/p>\n
    After setting up the cluster, start it:<\/p>\n
    <\/p>\n
    sudo pcs cluster start --all<\/code><\/pre>\n
    <\/p>\n
    Check the status:<\/p>\n
    <\/p>\n
    sudo pcs cluster status<\/code><\/pre>\n
    <\/p>\n
    Step 4: Configure Cluster Resources<\/h2>\n
    <\/p>\n
    With your Pacemaker cluster up and running, it’s time to configure resources that will failover between nodes. For example, if you want to manage an Apache web server, you would first create a resource for the Apache service:<\/p>\n
    <\/p>\n
    sudo pcs resource create WebServer apache configfile=\/etc\/httpd\/conf\/httpd.conf op start --timeout=60 --interval=0 op stop --timeout=60 --interval=0<\/code><\/pre>\n
    <\/p>\n
    You can also define constraints such as ensuring that the service is running on only one node at a time:<\/p>\n
    <\/p>\n
    sudo pcs resource master ms_WebServer WebServer 100<\/code><\/pre>\n
    <\/p>\n
    Step 5: Define Failover Policies and Constraints<\/h2>\n
    <\/p>\n
    In a high-availability setup, defining failover policies is crucial. You can configure options such as resource location, colocation, and ordering:<\/p>\n
    <\/p>\n
      <\/p>\n
    1. Colocation:<\/strong> Define where related resources must run together.<\/li>\n
      <\/p>\n
    2. Ordering:<\/strong> Define the order in which resources must start or stop.<\/li>\n
      \n<\/ol>\n
      <\/p>\n
      For example, to ensure your database starts before your web server:<\/p>\n
      <\/p>\n
      sudo pcs constraint order start ms_Database then start ms_WebServer<\/code><\/pre>\n
      <\/p>\n
      Step 6: Managing Cluster Resources<\/h2>\n
      <\/p>\n
      Once resources are configured, you can manage them using the pcs<\/code> commands:<\/p>\n
      <\/p>\n
      To start a resource:<\/p>\n
      <\/p>\n
      sudo pcs resource start WebServer<\/code><\/pre>\n
      <\/p>\n
      To stop a resource:<\/p>\n
      <\/p>\n
      sudo pcs resource stop WebServer<\/code><\/pre>\n
      <\/p>\n
      To check the status of resources:<\/p>\n
      <\/p>\n
      sudo pcs status resources<\/code><\/pre>\n
      <\/p>\n
      Step 7: Testing Your Configuration<\/h2>\n
      <\/p>\n
      To ensure that your HA setup is functioning correctly, test failover scenarios. You can simulate a node failure and observe if the resources migrate to the remaining node:<\/p>\n
      <\/p>\n
        <\/p>\n
      1. \n
        Stop the Pacemaker service on one of the nodes:<\/p>\n
        <\/p>\n
        sudo systemctl stop pacemaker<\/code><\/pre>\n
        \n<\/li>\n
        <\/p>\n
      2. \n
        Check the status on the remaining node to see if the resources have migrated.<\/p>\n
        \n<\/li>\n
        <\/p>\n
      3. \n
        Restart the Pacemaker service on the failed node:<\/p>\n
        <\/p>\n
        sudo systemctl start pacemaker<\/code><\/pre>\n
        \n<\/li>\n
        <\/p>\n
      4. Verify that the node rejoins the cluster and resources are redistributed appropriately.<\/li>\n
        \n<\/ol>\n
        <\/p>\n
        Conclusion<\/h2>\n
        <\/p>\n
        Configuring a high-availability cluster with Pacemaker on Linux is a straightforward process that significantly improves the reliability of your services. By following the steps outlined in this article, you’re well on your way to ensuring that your applications remain available even in the face of unforeseen failures.<\/p>\n
        <\/p>\n
        For further reading, explore the official Pacemaker documentation or consider additional resources on clustering technologies to enhance your understanding and capabilities.<\/p>\n
        <\/p>\n
        Additional Resources<\/h3>\n
        <\/p>\n