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

gds_check

Updated on 2022-07-29 GMT+08:00

Context

gds_check is used to check the GDS deployment environment, including the OS parameters, network environment, and disk usage. It also supports the recovery of system parameters. This helps detect potential problems during GDS deployment and running, improving the execution success rate.

Precautions

  • Set environment variables before executing the script. For details, see "Importing Data > Using a Foreign Table to Import Data In Parallel > Installing, Configuring, and Starting GDS" in the Developer Guide.
  • The script must be executed in the Python 3 environment.
  • This script must be run by user root.
  • The -t and --host parameters must be specified.
  • If --host specifies the network address 0.0.0.0 or 127.0.0.1, the MTU and NIC multi-queue are not checked.
  • The NIC multi-queue check and recovery require that the NIC be at least 10 GE.
  • The passwords of all nodes specified by the --host parameter must be the same so that the script can perform remote check successfully.
  • During the recovery, set the OS configuration items according to the recommended values. For details, see the following table.
    Table 1 OS configuration items

    Parameter

    Recommended Value

    net.core.somaxconn

    65535

    net.ipv4.tcp_max_syn_backlog

    65535

    net.core.netdev_max_backlog

    65535

    net.ipv4.tcp_retries1

    5

    net.ipv4.tcp_retries2

    12

    net.ipv4.ip_local_port_range

    26000 to 65535

    MTU

    1500

    net.core.wmem_max

    21299200

    net.core.rmem_max

    21299200

    net.core.wmem_default

    21299200

    net.core.rmem_default

    21299200

    max handler

    1000000

    vm.swappiness

    10

    Table 2 Disk check

    Check Item

    Warning

    Disk space usage

    Greater than or equal to 70% and less than 90%

    Inode usage

    Greater than or equal to 70% and less than 90%

    Table 3 Network conditions

    Check Item

    Error

    Network connectivity

    100% packet loss

    NIC multi-queue

    When NIC multi-queue is enabled and different CPUs are bound, fix can be modified.

Syntax

  • check command
    gds_check -t check --host [/path/to/hostfile | ipaddr1,ipaddr2...] --ping-host [/path/to/pinghostfile | ipaddr1,ipaddr2...] [--detail]
  • fix command
    gds_check -t fix --host [/path/to/hostfile | ipaddr1,ipaddr2...] [--detail]

Parameter Description

  • -t

    Operation type, indicating check or recovery.

    The value can be check or fix.

  • --host

    IP addresses of the nodes to be checked or recovered.

    Value: IP address list in the file or character string format

    • File format: Each IP address occupies a row, for example:

      192.168.1.200

      192.168.1.201

    • Character string format: IP addresses are separated by commas (,), for example:

      192.168.1.200,192.168.1.201

  • --ping-host

    Destination IP address for the network ping check on each node to be checked.

    Value: IP address list in the file or character string format. Generally, the value is the IP address of a DN, CN, or gateway.

    • File format: Each IP address occupies a row, for example:

      192.168.2.200

      192.168.2.201

    • Character string format: IP addresses are separated by commas (,), for example:

      192.168.2.200,192.168.2.201

  • --detail

    Displays detailed information about check and repair items and saves the information to logs.

  • -V

    Version information.

  • -h, --help

    Help information.

Examples

Perform a check. Both --host and --ping-host are in character string format.

gds_check -t check --host 192.168.1.100,192.168.1.101 --ping-host 192.168.2.100

Perform a check. --host is in character string format and --ping-host is in file format.

gds_check -t check --host 192.168.1.100,192.168.1.101 --ping-host /home/gds/iplist

cat /home/gds/iplist
192.168.2.100
192.168.2.101

Perform a check. --host is in file format and --ping-host is in character string format.

gds_check -t check --host  /home/gds/iplist --ping-host 192.168.1.100,192.168.1.101

Perform a recovery. --host is in character string format.

gds_check -t fix --host 192.168.1.100,192.168.1.101

Run the following command to perform the check, print the detailed information, and save the information to logs:

gds_check -t check --host 192.168.1.100 --detail

Run the following command to perform the repair, print the detailed information, and save the information to logs:

gds_check -t fix --host 192.168.1.100 --detail

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