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

ALM-14011 DataNode Data Directory Is Not Configured Properly

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

Description

The DataNode parameter dfs.datanode.data.dir specifies DataNode data directories. This alarm is generated when a configured data directory cannot be created, a data directory uses the same disk as other critical directories in the system, or multiple directories use the same disk immediately.

This alarm is cleared when the DataNode data directory is configured properly and this DataNode for which the alarm is generated is restarted.

Attribute

Alarm ID

Alarm Severity

Automatically Cleared

14011

Major

Yes

Parameters

Name

Meaning

Source

Specifies the cluster for which the alarm is generated.

ServiceName

Specifies the service for which the alarm is generated.

RoleName

Specifies the role for which the alarm is generated.

HostName

Specifies the host for which the alarm is generated.

Impact on the System

If the DataNode data directory is mounted to the root directory or a critical directory, the disk space of the root directory or critical directory will be used up after long time running and the system will be faulty.

If the DataNode data directory is not configured properly, HDFS performance will deteriorate.

Possible Causes

  • The DataNode data directory fails to be created.
  • The DataNode data directory uses the same disk with critical directories, such as / or /boot.
  • Multiple directories in the DataNode data directory use the same disk.

Procedure

Check the alarm cause and information about the DataNode for which the alarm is generated.

  1. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms. In the alarm list, click the alarm.
  2. In HostName of Location, obtain the host name of the DataNode for which the alarm is generated.

Delete directories that do not comply with the disk plan from the DataNode data directory.

  1. Choose Cluster > Name of the desired cluster > Services > HDFS > Instance. In the instance list, click the DataNode instance on the node for which the alarm is generated.
  2. Click Instance Configurations and view the value of the DataNode parameter dfs.datanode.data.dir.
  3. Check whether all DataNode data directories are consistent with the disk plan.

    • If yes, go to 6.
    • If no, go to 9.

  4. Modify the DataNode parameter dfs.datanode.data.dir and delete the incorrect directories.
  5. Choose Cluster > Name of the desired cluster > Services > HDFS > Instance and restart the DataNode instance.
  6. Check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 9.

  7. Log in to the DataNode for which the alarm is generated as user root.

    • If the alarm cause is "The DataNode data directory fails to be created", go to 10.
    • If the alarm cause is "The DataNode data directory uses the same disk with critical directories, such / or /boot", go to 17.
    • If the alarm cause is "Multiple directories in the DataNode data directory uses the same disk", go to 21.

Check whether the DataNode data directory fails to be created.

  1. Run the su - omm command to switch to user omm.
  2. Run the ls command to check whether the directories exist in the DataNode data directory.

    • If yes, go to 26.
    • If no, go to 12.

  3. Run the mkdir data directory command to create the directory and check whether the directory can be successfully created.

    • If yes, go to 24.
    • If no, go to 13.

  4. On the FusionInsight Manager portal, choose O&M > Alarm > Alarms to check whether alarm ALM-12017 Insufficient Disk Capacity exists.

    • If yes, go to 14.
    • If no, go to 15.

  5. Adjust the disk capacity and check whether alarm ALM-12017 Insufficient Disk Capacity is cleared. For details, see ALM-12017 Insufficient Disk Capacity.

    • If yes, go to 12.
    • If no, go to 15.

  6. Check whether user omm has the rwx or x permission of all the upper-layer directories of the directory. (For example, for /tmp/abc/, user omm has the x permission for directory tmp and the rwx permission for directory abc.)

    • If yes, go to 24.
    • If no, go to 16.

  7. Run the chmod u+rwx path or chmod u+x path command as user root to assign the rwx or x permission of these directories to user omm. Then go to 12.

Check whether the DataNode data directory use the same disk as other critical directories in the system.

  1. Run the df command to obtain the disk mounting information of each directory in the DataNode data directory.
  2. Check whether the directories mounted to the disk are critical directories, such as / or /boot.

    • If yes, go to 19.
    • If no, go to 24.

  3. Change the value of the DataNode parameter dfs.datanode.data.dir and delete the directories that use the same disk as critical directories.
  4. Go to 24.

Check whether multiple directories in the DataNode data directory use the same disk.

  1. Run the df command to obtain the disk mounting information of each directory in the DataNode data directory. Record the mounted directory in the command output.
  2. Modify the DataNode node parameters dfs.datanode.data.dir to reserve only one directory among the directories that mounted to the same disk directory.
  3. Go to 24.

Restart the DataNode and check whether the alarm is cleared.

  1. On the FusionInsight Manager portal, choose Cluster > Name of the desired cluster > Services > HDFS > Instance and restart the DataNode instance
  2. Check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 26.

Collect fault information.

  1. On the FusionInsight Manager portal, choose O&M > Log > Download.
  2. Select HDFS in the required cluster from the Service.
  3. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
  4. Contact the O&M personnel and send the collected logs.

Alarm Clearing

After the fault is rectified, the system automatically clears this alarm.

Related Information

None

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