このページは、お客様の言語ではご利用いただけません。Huawei Cloudは、より多くの言語バージョンを追加するために懸命に取り組んでいます。ご協力ありがとうございました。

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
Situation Awareness
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

Adding a New Disk to an MRS Cluster

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

Issue

MRS HBase is unavailable.

Symptom

A high disk usage of the user's host causes service faults.

Cause Analysis

The service becomes unavailable due to insufficient disk capacity of the core node.

Procedure

  1. Purchase an EVS disk.
  2. Attach the EVS disk.

    • If the EVS disk has been attached, go to 6.
    • If an ECS cannot be selected when you attach the EVS disk on the EVS console, go to 3.

  3. Log in to the ECS console and click the name of the ECS to which the new disk is to be attached.
  4. On the Disks tab, click Attach Disk.
  5. Select the new disk to be attached and click OK.
  6. Initialize a Linux data disk.

    NOTE:
    • The mount point directory is the existing DataNode instance ID plus one. For example, if you run the df –h command and find that the existing ID is /srv/BigData/hadoop/data1, the new mount point is then /srv/BigData/hadoop/data2. When initializing a Linux data disk to create a mount point, name the mount point /srv/BigData/hadoop/data2 and mount a new partition to the mount point. For example:
      mkdir /srv/BigData/hadoop/data2
      mount /dev/xvdb1 /srv/BigData/hadoop/data2
    About the /srv/BigData/hadoop/data2 path: Change /srv/BigData/hadoop/data2 mentioned below according to the following scenarios:
    • In 3.x: Change it to /srv/BigData/data2.
    • In versions earlier than 3.x : Change it to /srv/BigData/hadoop/data2.

  7. Run the following command to grant user omm the permissions to access the new disk:

    chown omm:wheel New mount point

    Example: chown omm:wheel /srv/BigData/hadoop/data2

  8. Run the following command to grant the execution permission on the new mount point directory:

    chmod 701 New mount point

    Example: chmod 701 /srv/BigData/hadoop/data2

    NOTE:

    In this command, 701 is only an example. Replace it with the value of the existing data disk data1.

  9. Log in to Manager and add data disks to DataNode and NodeManager instances.
  10. Modify the DataNode instance configuration.

    MRS Manager: Log in to MRS Manager, choose Services > HDFS > Instance, click the target DataNode instance, and click Instance Configuration. On the displayed page, set Type to All.

    FusionInsight Manager: Log in to FusionInsight Manager and choose Cluster. Click the name of the desired cluster and choose Service > HDFS > Instance. Click the target DataNode instance, click Instance Configuration, and select All Configurations.

    • Method 1: Manually modify the DataNode instance configuration on the current node.
      • Enter dfs.datanode.fsdataset.volume.choosing.policy in the search box and change the parameter value to org.apache.hadoop.hdfs.server.datanode.fsdataset.AvailableSpaceVolumeChoosingPolicy.
      • Enter dfs.datanode.data.dir in the search box and change the parameter value to /srv/BigData/hadoop/data1/dn,/srv/BigData/hadoop/data2/dn.

      If the values of the two parameters have been changed, click Save Configuration and select Restart role instance to restart the DataNode instance.

    • Method 2: Automatically synchronize the DataNode instance configuration on the current node.
      1. Click Synchronize Configuration to enable the new configuration for the HDFS service.
      2. After the synchronization is complete, restart the instance for the configuration to take effect.
    NOTE:
    • If HDFS is not used and you want to quickly restart the instance, select Restart role instance.
    • If a task is using HDFS, you must select rolling restart to prevent data exceptions or task failures.

  11. Modify the Yarn NodeManager instance configuration.

    MRS Manager: Log in to MRS Manager, choose Services > Yarn > Instance, click the target NodeManager instance, and click Instance Configuration. On the displayed page, set Type to All.

    FusionInsight Manager: Log in to FusionInsight Manager and choose Cluster. Click the name of the desired cluster and choose Service > Yarn > Instance. Click the target NodeManager instance, click Instance Configuration, and select All Configurations.

    • Method 1: Manually modify the Yarn NodeManager instance configuration on the current node.
      • Enter yarn.nodemanager.local-dirs in the search box and change the parameter value to /srv/BigData/hadoop/data1/nm/localdir,/srv/BigData/hadoop/data2/nm/localdir.
      • Enter yarn.nodemanager.log-dirs in the search box and change the parameter value to /srv/BigData/hadoop/data1/nm/containerlogs,/srv/BigData/hadoop/data2/nm/containerlogs.

        If the values of the two parameters have been changed, click Save Configuration and select Restart role instance to restart the NodeManager instance.

    • Method 2: Automatically synchronize the Yarn NodeManager instance configuration on the current node.
      1. Click Synchronize Configuration to enable the new configuration for the Yarn service.
      2. After the synchronization is complete, restart the instance for the configuration to take effect.

    NOTE:
    • If Yarn is not used and you want to quickly restart the instance, select Restart role instance.
    • If a task is using Yarn, you must select rolling restart to prevent data exceptions or task failures.

  12. Check whether the capacity expansion is successful.

    MRS Manager: Log in to MRS Manager, choose Services > HDFS > Instance, and click the target DataNode instance.

    FusionInsight Manager: Log in to FusionInsight Manager and choose Cluster. Click the name of the desired cluster, choose Service > HDFS > Instance, and click the target DataNode instance.

    In the Chart area, check whether the total disk capacity in real-time monitoring item DataNode Storage is increased. If DataNode Storage does not exist in the Chart area, click Customize to add it.
    • If the total disk capacity has been increased, the capacity expansion is complete.
    • If the total disk capacity does not increase, contact technical support.

  13. (Optional) Add data disks to a Kafka instance.

    Modify the Kafka instance configuration.

    1. Navigate to the parameter settings of the target Kafka Broker node.

      MRS Manager: Log in to MRS Manager, choose Services > Kafka > Instance, click the target Broker instance, and click Instance Configuration. On the displayed page, set Type to All.

      FusionInsight Manager: Log in to FusionInsight Manager and choose Cluster. Click the name of the desired cluster and choose Service > Kafka > Instance. Click the target Broker instance, click Instance Configuration, and select All Configurations.

    2. Enter log.dirs in the search box, add information about the disks to be added, and use commas (,) to separate them.

      For example, if there is only one existing Kafka data disk and a new one is added, change /srv/BigData/kafka/data1/kafka-logs to /srv/BigData/kafka/data1/kafka-logs,/srv/BigData/kafka/data2/kafka-logs.

    3. Save the configuration and select Restart role instance to restart the instance as prompted.
    4. Check whether the capacity expansion is successful.

      MRS Manager: Log in to MRS Manager, choose Services > Kafka > Instance, and click the target Broker instance.

      FusionInsight Manager: Log in to FusionInsight Manager and choose Cluster. Click the name of the desired cluster, choose Service > Kafka > Instance, and click the target Broker instance.

      Check whether the total disk capacity in real-time monitoring item Capacity of Broker Disks is increased.

NOTICE:

After the disk capacity of a cluster node is expanded, if a new node is added to the cluster, you need to add disks to the new node by referring to the preceding procedure. Otherwise, data may be lost.

Summary and Suggestions

  • If the disk usage exceeds 85%, you are advised to expand disk capacity and attach the newly purchased disks to ECSs to associate with the cluster.
  • The procedure for attaching disks and setting parameters may vary depending on the site environment.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback