Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.

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
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
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Scalable File Service Turbo
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
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/ MRS Cluster O&M/ MRS Cluster Alarm Handling Reference/ ALM-45641 Data Synchronization Exception Between the Active and Standby FlinkServer Nodes

ALM-45641 Data Synchronization Exception Between the Active and Standby FlinkServer Nodes

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

This section applies to MRS 3.2.0 or later.

Alarm Description

The system checks data synchronization between the active and standby FlinkServer nodes every 60 seconds. This alarm is generated when the standby FlinkServer node fails to synchronize files with the active FlinkServer node.

This alarm is cleared when the standby FlinkServer synchronizes files with the active FlinkServer.

Alarm Attributes

Alarm ID

Alarm Severity

Auto Cleared

45641

Major

Yes

Alarm Parameters

Parameter

Description

Source

Specifies the cluster or system for which the alarm was generated.

ServiceName

Specifies the service for which the alarm was generated.

RoleName

Specifies the role for which the alarm was generated.

HostName

Specifies the host for which the alarm was generated.

Impact on the System

After an active/standby switchover, some configurations may be lost. Some jobs and connections of the FlinkServer are interrupted, but the FlinkServer can still provide services properly.

Possible Causes

  • The link between the active and standby FlinkServer nodes is interrupted.
  • The synchronization file does not exist or the file permission is required.

Handling Procedure

Check whether the network between the active and standby FlinkServer is in normal state.

  1. On FusionInsight Manager, choose Cluster > Services > ClickHouse > Instance. View and record the IP addresses of active and standby FlinkServer.
  2. Log in to the active FlinkServer node as the root user.
  3. Run the following command to check whether the standby FlinkServer is reachable:

    ping IP address of the standby FlinkServer

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

  4. Contact the network administrator to check whether the network is faulty.

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

  5. Rectify the network fault and check whether the alarm is cleared from the alarm list.

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

Check whether the storage space of the /srv/BigData/LocalBackup directory is insufficient.

  1. Run the following command to check whether the storage space of the /srv/BigData/LocalBackup directory is insufficient:

    df -hl /srv/BigData/LocalBackup
    • If yes, go to 7.
    • If no, go to 10.

  2. Run the following command to clear unnecessary backup files:

    rm -rf Directory to be cleared

    The following are two examples:

    rm -rf /srv/BigData/LocalBackup/0/default-oms_20191211143443

  3. On FusionInsight Manager, choose O&M > Backup and Restoration > Backup Management.

    In the Operation column of the backup task, click Configure and change the value of Maximum Number of Backup Copies to reduce the number of backup file sets.

  4. Wait for 1 minute and check whether the alarm is cleared.

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

Check whether the synchronization file exists and whether the file permission is valid.

  1. Run the following command to check whether the synchronization file exists:

    find /srv/BigData/ -name "sed*"

    find /opt -name "sed*"

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

  2. Run the following command to check the synchronization file information and permission queried in 10:

    ll Path of the file you want to search for

    • If the file size is 0 and all values in the permission column are -, the file is a junk file. Run the following command to delete it:

      rm -rf Files to be deleted

      Wait for several minutes and check whether the alarm is cleared. If the alarm persists, go to 12.

    • If the file size is not 0, go to 12.

  3. View the log file generated when the alarm is reported.

    1. Run the following command to go to the HA run log file path of the current cluster:

      cd /var/log/Bigdata/flink/flinkserver/ha/runlog

    2. Decompress log file and view the logs generated when the alarm is reported.

      For example, if the name of the file is ha.log.2021-03-22_12-00-07.gz, run the following command:

      gunzip ha.log.2021-03-22_12-00-07.gz

      vi ha.log.2021-03-22_12-00-07

      Check whether error information is displayed before and after the alarm generation time in the logs.

      • If it is displayed, rectify the fault based on the error information. Go to 13.

        For example, if the following error information is displayed, the directory permission is required. In this case, obtain the directory permission that is the same as the permission on a normal node.

      • If no, go to 14.

  4. Wait for about 10 minutes and check whether the alarm is cleared.

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

Collect fault information.

  1. On FusionInsight Manager, choose O&M > Log > Download.
  2. Select FlinkServer information from Services and click OK.
  3. Expand the Hosts drop-down list. In the Select Host dialog box that is displayed, select the hosts to which the role belongs, and click OK.
  4. 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.
  5. Contact O&M personnel and provide the collected logs.

Alarm Clearance

This alarm is automatically cleared after the fault is rectified.

Related Information

None

Sitemizi ve deneyiminizi iyileştirmek için çerezleri kullanırız. Sitemizde tarama yapmaya devam ederek çerez politikamızı kabul etmiş olursunuz. Daha fazla bilgi edinin

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback