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
Help Center/ MapReduce Service/ User Guide/ Managing Clusters/ Managing an MRS Cluster/ Replacing the NTP Server for an MRS Cluster

Replacing the NTP Server for an MRS Cluster

Updated on 2024-09-23 GMT+08:00

If no NTP server is configured or the configured NTP server is no longer used, you can specify a new NTP server for the MRS cluster or replace the NTP server with a new one to enable the cluster to synchronize time with the new NTP clock source.

NOTE:

This section applies only to MRS 3.x or later.

Prerequisites

  • You have prepared a new NTP server and obtained its IP address, and have configured the network between the cluster and the new NTP server.
  • Ensure that the NTP service status of the server is normal. Otherwise, the operations in this section will fail.

Impact on the System

  • Replacing the NTP server is a high-risk operation and may result in time change in the cluster.
  • If the time difference between the NTP server and the cluster is greater than 150s before the NTP server replacement, you need to stop the cluster first to prevent data loss. Services are unavailable when the cluster is stopped.
  • If the time difference between the NTP server and the cluster exceeds 15 minutes, the cluster will be unable to access OBS.
  • If your clusters use Kerberos authentication and the time difference between the NTP server and the cluster exceeds 5 minutes, authentication will not work.

Modifying the NTP Server of an MRS Cluster

  1. Log in to FusionInsight Manager and check whether there are uncleared alarms.

    • If yes, clear the alarm. After the alarm is cleared, go to 2.
    • If no, go to 2.

  2. Log in to the active and standby management nodes as user omm.
  3. Run the following command on the active management node to check the management plane gateway:

    cat ${BIGDATA_HOME}/om-server/OMS/workspace/conf/oms-config.ini | grep om_gateway

  4. Run the ping Management plane gateway command on the active and standby management nodes and check whether the nodes are connected to the management plane gateway.

    • If yes, go to 5.
    • If no, contact the network administrator to rectify the network fault. After the fault is rectified, go to 5.

  5. Run the following command on the active management node to obtain the domain name of the NTP server in the current environment:

    This section uses ntp.myhuaweicloud.com as an example.

    cat /opt/Bigdata_func/cloudinit/cloudinit_params | grep ntpserver

  6. On the active management node, check the time difference between the new NTP server and the cluster. The unit is second.

    For example, to check the time different with the NTP server at ntp.myhuaweicloud.com, run the ntpdate -d ntp.myhuaweicloud.com command. The following information is displayed:

     6 Dec 15:16:10 ntpdate[2861453]: step time server 10.79.3.251 offset +2.118107 sec
    In the preceding information, +2.118107 sec indicates the time offset. A positive value indicates that the NTP server time is earlier than the current cluster time. A negative value indicates the opposite.
    • NOTE:

      You can run the ntpq -v or ntpq --version command to query the NTP version. The command output may vary with the actual service environment.

      • Output of the ntpq -v command:
        10.1.1.112: ~# ntpq -v
        ntpq - standard NTP query program - Ver. 4.2.4p8
      • Output of the ntpq --version command:
        10.1.1.112: ~# ntpq --version
        ntpq 4.2.8p10@1.3728-o Mon Jun  6 08:01:59 UTC 2016 (1)

  7. Check whether the absolute value of the time difference exceeds 150.

    • If yes, go to 8.
    • If no, perform 10 as user omm.

  8. Check whether the cluster can be stopped.

    • If yes, stop upper-layer services and the cluster, and go to 9.
    • If no, no further action is required.

  9. Check whether the time of the NTP server is slower than the time of the cluster.

    • If yes, wait a period of the time difference obtained in 6 after message Operation successful is displayed on the UI, perform 11 as user omm.
    • If no, after message Operation successful is displayed on the UI, perform 11 as user omm.

  10. Run the following command on the active management node to replace the NTP server:

    sh ${BIGDATA_HOME}/om-server/om/bin/tools/modifyntp.sh --ntp_server_ip ntp.myhuaweicloud.com

    NOTE:

    The IP address of the NTP server cannot be set to the IP address of a node in the cluster. Otherwise, the service network between the node and the active/standby OMS node may be disconnected.

  11. Run the following command on the active management node to forcibly synchronize time from the NTP server at ntp.myhuaweicloud.com immediately and replace the NTP server:

    sh ${BIGDATA_HOME}/om-server/om/bin/tools/modifyntp.sh --ntp_server_ip ntp.myhuaweicloud.com --force_sync_time

    NOTE:
    • If the cluster is stopped, start the cluster after the NTP server is replaced.
    • After the command for forcible time synchronization is executed, it takes about five minutes for time synchronization on cluster nodes.

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