Help Center/ MapReduce Service/ Component Operation Guide (Paris Region)/ Using HBase/ Performing an HBase DR Service Switchover
Updated on 2022-12-14 GMT+08:00
View PDF
Share

Performing an HBase DR Service Switchover

Scenario

You can configure HBase cluster DR to improve system availability. If the active cluster in the DR environment is faulty and the connection to the HBase upper-layer application is affected, you need to configure the standby cluster information for the HBase upper-layer application so that the application can run in the standby cluster.

This section applies to MRS 3.x or later clusters.

Impact on the System

After a service switchover, data written to the standby cluster is not synchronized to the active cluster by default. Add the active cluster is recovered, the data newly generated in the standby cluster needs to be synchronized to the active cluster by backup and recovery. If automatic data synchronization is required, you need to switch over the active and standby HBase DR clusters.

Procedure

  1. Log in to FusionInsight Manager of the standby cluster.
  2. Download and install the HBase client.

  3. On the HBase client of the standby cluster, run the following command as user hbase to enable the data writing status in the standby cluster.

    kinit hbase

    hbase shell

    set_clusterState_active

    The command is run successfully if the following information is displayed:

    hbase(main):001:0> set_clusterState_active
=> true

  4. Check whether the original configuration files hbase-site.xml, core-site.xml, and hdfs-site.xml of the HBase upper-layer application are modified to adapt to the application running.

    • If yes, update the related content to the new configuration file and replace the old configuration file.
    • If no, use the new configuration file to replace the original configuration file of the HBase upper-layer application.

  5. Configure the network connection between the host where the HBase upper-layer application is located and the standby cluster.

    If the host where the client is installed is not a node in the cluster, configure network connections for the client to prevent errors when you run commands on the client.

    1. Ensure that the host where the client is installed can communicate with the hosts listed in the hosts file in the directory where the client installation package is decompressed.
    2. If the host where the client is located is not a node in the cluster, you need to set the mapping between the host name and the IP address (service plan) in the /etc/hosts file on the host. The host names and IP addresses must be mapped one by one.

  6. Set the time of the host where the HBase upper-layer application is located to be the same as that of the standby cluster. The time difference must be less than 5 minutes.
  7. Check the authentication mode of the active cluster.

    • If the security mode is used, go to 8.
    • If the normal mode is used, no further action is required.

  8. Obtain the keytab and krb5.conf configuration files of the HBase upper-layer application user.

    1. On FusionInsight Manager of the standby cluster, choose System > Permission > User.
    2. Locate the row that contains the target user, click More > Download Authentication Credential in the Operation column, and download the keytab file to the local PC.
    3. Decompress the package to obtain user.keytab and krb5.conf.

  9. Use the user.keytab and krb5.conf files to replace the original files in the HBase upper-layer application.
  10. Stop upper-layer applications.
  11. Determine whether to switch over the active and standby HBase clusters. If the switchover is not performed, data will not be synchronized.

  12. Start the upper-layer services.
Parent topic: Using HBase