No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionInsight HD 6.5.0 Administrator Guide 02

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Recovering Kafka Metadata

Recovering Kafka Metadata

Scenario

Kafka metadata needs to be recovered in the following scenarios: Data is modified or deleted unexpectedly and needs to be restored; after an administrator performs a critical operation (such as upgrade and critical data adjustment) on ZooKeeper, an exception occurs or the operation has not achieved the expected result; all Kafka modules are faulty and become unavailable; data is migrated to a new cluster.

System administrators can create a recovery task in FusionInsight Manager to recover Kafka data. Only manual recovery tasks are supported.

  • Data recovery can be performed only when the system version is consistent with that of data backup.
  • To recover Kafka metadata when the service is running properly, you are advised to manually back up the latest Kafka metadata before recovery. Otherwise, the Kafka metadata that is generated after the data backup and before the data recovery will be lost.

Impact on the System

  • After the metadata is recovered, the data generated between the backup point in time and the recovery point in time is lost.
  • After the metadata is recovered, the offset information stored on ZooKeeper by Kafka consumers is restored to a previous state, resulting in repeated consumption.

Prerequisites

  • If the active cluster employs the security mode, cross-cluster trust relationship has been configured for the active and standby clusters. For details, see Configuring Cross-Cluster Mutual Trust Relationships. If the active cluster employs the normal mode, no cross-cluster trust relationship is required.
  • Cross-cluster replication has been configured for the active and standby clusters. For details, see Enabling Cross-Cluster Replication.
  • The time of the active cluster and standby cluster must be the same, and the NTP service in the active and standby clusters must use the same time source.
  • The Kafka service is disabled first, and then enabled upon data recovery.
  • You have logged in to FusionInsight Manager. For details, see Logging In to the Management System.

Procedure

  1. On FusionInsight Manager, choose O&M > Backup and Restoration > Backup Management.
  2. In the Operation column of a specified task in the task list, click More > View History to view historical backup task execution records.

    In the displayed window, locate a specified success record and click View in the Backup Path column to view the backup path information of the task and find the following information:

    • Backup Object specifies the data source of the backup data.
    • Backup Path specifies the full path where the backup files are saved.

      Select the correct item, and manually copy the full path of backup files in Backup Path.

  3. On FusionInsight Manager, choose O&M > Backup and Restoration > Restoration Management.
  4. Click Create.
  5. Set Task Name to the name of the recovery task.
  6. Select Kafka in Restoration Configuration.

    NOTE:

    If there are multiple Kafka services, you can specify the Kafka to be revocered.

  7. Set Path Type of Kafka to a backup directory type.

    The settings vary according to backup directory types:

    • LocalDir: indicates that the backup files are stored on the local disk of the active management node. If you select this value, you need to set Source Path to select the backup file, for example, version_data source_task execution time.tar.gz.
    • LocalHDFS: indicates that the backup files are stored in the HDFS directory of the current cluster. If you select this value, you need to set the following parameters:
      • Source Path: indicates the full path of the backup file in HDFS, for example, backup path/backup task name_task creation time/version_data source_task execution time.tar.gz.
      • Source NameService Name: indicates the NameService name that corresponds to the backup directory when the recovery task is executed. The default value is hacluster.
    • RemoteHDFS: indicates that the backup files are stored in the HDFS directory of the standby cluster. If you select this value, you need to set the following parameters:
      • Target NameNode IP Address: indicates the NameNode service plane IP address of the standby cluster, supporting the active node or standby node.
      • Source Path: indicates the full path of the HDFS directory for storing standby cluster backup data. For example, backup path/backup task name_data source_task creation time/version_data source_task execution time.tar.gz.
      • Queue Name: indicates the name of the YARN queue used for backup task execution. The name must be the same as the name of the queue that is running properly in the cluster.
    • NFS: indicates that backup files are stored in the NAS over the NFS protocol. If you select NFS, set the following parameters:
      • Server IP address: indicates the NAS server IP address.
      • Source Path: indicates the complete path of the backup file on the NAS server. For example, backup path/backup task name_data source_task creation time/version_data source_task execution time.tar.gz.
    • CIFS: indicates that backup files are stored in the NAS over the CIFS protocol. If you select CIFS, set the following parameters:
      • Server IP address: indicates the NAS server IP address.
      • Port: indicates the port ID used by the CIFS protocol to connect to the NAS server. The default value is 445.
      • Username: Indicates the user name that is configured when setting the CIFS protocol.
      • Password: indicates the password that is configured when setting the CIFS protocol.
      • Source Path: indicates the complete path of the backup file on the NAS server. For example, backup path/backup task name_data source_task creation time/version_data source_task execution time.tar.gz.

  8. Click OK to save the settings.
  9. In the recovery task list, locate a created task and click Start in the Operation column to execute the recovery task.

    • After the recovery is successful, the progress bar is in green.
    • After the recovery is successful, the recovery task cannot be executed again.
    • If the recovery task fails during the first execution, rectify the fault and click Retry to execute the task again.

Download
Updated: 2019-05-17

Document ID: EDOC1100074522

Views: 6112

Downloads: 12

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next