El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Recovering Kafka Metadata

Updated on 2022-08-12 GMT+08:00

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.

NOTICE:
  • 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

  • To restore data from the remote HDFS, you need to prepare the standby cluster. If the active cluster is deployed in security mode and the active and standby clusters are not managed by the same FusionInsight Manager, configure system mutual trust. For details, see Configuring Cross-Manager Cluster Mutual Trust Relationships. If the active cluster is deployed in normal mode, do not configure mutual trust.
  • 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 FusionInsight Manager.

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 the cluster to be operated from Recovery Object.
  7. Select Kafka in Restoration Configuration.

    NOTE:

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

  8. 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:
      • Source NameService Name: indicates the NameService name of the backup data cluster. You can set it to the NameService name (haclusterX, haclusterX1, haclusterX2, haclusterX3, or haclusterX4) of the built-in remote cluster of the cluster, or the NameService name of a configured remote cluster.
      • IP Mode: mode of the target IP address.The system automatically selects the IP address mode based on the cluster network type, for example, IPv4 or IPv6.
      • Source 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:
      • IP Mode: mode of the target IP address.The system automatically selects the IP address mode based on the cluster network type, for example, IPv4 or IPv6.
      • 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:
      • IP Mode: mode of the target IP address.The system automatically selects the IP address mode based on the cluster network type, for example, IPv4 or IPv6.
      • 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.
    • OBS: indicates that the backup files are stored in the OBS directory.
      If you select this value, you need to set the following parameters:
      • Source Path: indicates the full path for storing backup data in OBS. For example, backup path/backup task name_data source_task creation time/version_data source_task execution time.tar.gz.
        NOTE:

        MRS 3.1.0 and later versions support saving backup files to OBS.

  9. Click OK to save the settings.
  10. 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.

Utilizamos cookies para mejorar nuestro sitio y tu experiencia. Al continuar navegando en nuestro sitio, tú aceptas nuestra política de cookies. Descubre más

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback