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

Updating a Client (Versions Earlier Than 3.x)

Updated on 2022-02-22 GMT+08:00
NOTE:

This section applies to clusters of versions earlier than MRS 3.x. For MRS 3.x or later, see Updating a Client (Version 3.x or Later).

Updating a Client Configuration File

Scenario

An MRS cluster provides a client for you to connect to a server, view task results, or manage data. Before using an MRS client, you need to download and update the client configuration file if service configuration parameters are modified and a service is restarted or the service is merely restarted on MRS Manager.

During cluster creation, the original client is stored in the /opt/client directory on all nodes in the cluster by default. After the cluster is created, only the client of a Master node can be directly used. To use the client of a Core node, you need to update the client configuration file first.

Procedure

Method 1:

  1. Log in to MRS Manager. For details, see Accessing Manager. Then, choose Services.
  2. Click Download Client.

    Set Client Type to Only configuration files, Download To to Server, and click OK to generate the client configuration file. The generated file is saved in the /tmp/MRS-client directory on the active management node by default. You can customize the file path.

  3. Query and log in to the active Master node.
  4. If you use the client in the cluster, run the following command to switch to user omm. If you use the client outside the cluster, switch to user root.

    sudo su - omm

  5. Run the following command to switch to the client directory, for example, /opt/Bigdata/client:

    cd /opt/Bigdata/client

  6. Run the following command to update client configurations:

    sh refreshConfig.sh Client installation directory Full path of the client configuration file package

    For example, run the following command:

    sh refreshConfig.sh /opt/Bigdata/client /tmp/MRS-client/MRS_Services_Client.tar

    If the following information is displayed, the configurations have been updated successfully.

    ReFresh components client config is complete.
    Succeed to refresh components client config.

Method 2:

  1. After the cluster is installed, run the following command to switch to user omm. If you use the client outside the cluster, switch to user root.

    sudo su - omm

  2. Run the following command to switch to the client directory, for example, /opt/Bigdata/client:

    cd /opt/Bigdata/client

  3. Run the following command and enter the name of an MRS Manager user with the download permission and its password (for example, the username is admin and the password is the one set during cluster creation) as prompted to update client configurations.

    sh autoRefreshConfig.sh

  4. After the command is executed, the following information is displayed, where XXX indicates the name of the component installed in the cluster. To update client configurations of all components, press Enter. To update client configurations of some components, enter the component names and separate them with commas (,).

    Components "xxx" have been installed in the cluster. Please input the comma-separated names of the components for which you want to update client configurations. If you press Enter without inputting any component name, the client configurations of all components will be updated:

    If the following information is displayed, the configurations have been updated successfully.

    Succeed to refresh components client config.

    If the following information is displayed, the username or password is incorrect.

    login manager failed,Incorrect username or password.
    NOTE:
    • This script automatically connects to the cluster and invokes the refreshConfig.sh script to download and update the client configuration file.
    • By default, the client uses the floating IP address specified by wsom=xxx in the Version file in the installation directory to update the client configurations. To update the configuration file of another cluster, modify the value of wsom=xxx in the Version file to the floating IP address of the corresponding cluster before performing this step.

Fully Updating the Original Client of the Active Master Node

Scenario

During cluster creation, the original client is stored in the /opt/client directory on all nodes in the cluster by default. The following uses /opt/Bigdata/client as an example.

  • For a normal MRS cluster, you will use the pre-installed client on a Master node to submit a job on the management console page.
  • You can also use the pre-installed client on the Master node to connect to a server, view task results, and manage data.

After installing the patch on the cluster, you need to update the client on the Master node to ensure that the functions of the built-in client are available.

Procedure

  1. Log in to MRS Manager. For details, see Accessing Manager. Then, choose Services.
  2. Click Download Client.

    Set Client Type to All client files, Download To to Server, and click OK to generate the client configuration file. The generated file is saved in the /tmp/MRS-client directory on the active management node by default. You can customize the file path.

  3. Query and log in to the active Master node.
  4. On the ECS, switch to user root and copy the installation package to the /opt directory.

    sudo su - root

    cp /tmp/MRS-client/MRS_Services_Client.tar /opt

  5. Run the following command in the /opt directory to decompress the package and obtain the verification file and the configuration package of the client:

    tar -xvf MRS_Services_Client.tar

  6. Run the following command to verify the configuration file package of the client:

    sha256sum -c MRS_Services_ClientConfig.tar.sha256

    The command output is as follows:

    MRS_Services_ClientConfig.tar: OK

  7. Run the following command to decompress MRS_Services_ClientConfig.tar:

    tar -xvf MRS_Services_ClientConfig.tar

  8. Run the following command to move the original client to the /opt/Bigdata/client_bak directory:

    mv /opt/Bigdata/client /opt/Bigdata/client_bak

  9. Run the following command to install the client in a new directory. The client path must be /opt/Bigdata/client.

    sh /opt/MRS_Services_ClientConfig/install.sh /opt/Bigdata/client

    If the following information is displayed, the client has been successfully installed:

    Components client installation is complete.

  10. Run the following command to modify the user and user group of the /opt/Bigdata/client directory:

    chown omm:wheel /opt/Bigdata/client -R

  11. Run the following command to configure environment variables:

    source /opt/Bigdata/client/bigdata_env

  12. If Kerberos authentication is enabled for the current cluster, run the following command to authenticate the user. If Kerberos authentication is disabled for the current cluster, skip this step.

    kinit MRS cluster user

    Example: kinit admin

  13. Run the client command of a component.

    For example, run the following command to query the HDFS directory:

    hdfs dfs -ls /

Fully Updating the Original Client of the Standby Master Node

  1. Repeat 1 to 3 to log in to the standby Master node, and run the following command to switch to user omm:

    sudo su - omm

  2. Run the following command on the standby Master node to copy the downloaded client package from the active Master node (master1 is used as an example):

    scp omm@master1_host_name:/tmp/MRS-client/MRS_Services_Client.tar /tmp/MRS-client/

  3. Repeat 4 to 13 to update the client of the standby Master node.

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