tencent cloud

TencentDB for MariaDB

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Strengths
Use Cases
System Architecture
Instance Types
Instance Architecture
TDSQL Edition
Database Version
Purchase Guide
Billing Overview
Pricing
Refund
Payment Overdue
Upgrade Pricing
Backup Space Billing
Getting Started
Creating Instance
Managing Account
Accessing Instance
Operation Guide
Precautions
Instance Management
Disaster Recovery Read-Only Instance
Account Management
Read/Write Separation
Changing Networks
Backup and Rollback
Migrating Data
Database Sync(Legacy)
Security Management
Monitoring and Alarms
Killing Threads
Parameter Templates and Settings
Database Audit
Practical Tutorial
Programming and Usage Specification
Programming and Usage Specification of Distributed Version
Using Hotspot Update for Flash Sales
Security White Paper
Platform Security Features
Tenant Security Features
Development Guide
Functional Limitations
Performance Test
Intra-city Active-Active Solution
Binlog Consumption Format
Slow Query Analysis
Database Audit
Syntax Supported
API Documentation
History
Introduction
API Category
Making API Requests
Security Group APIs
Other APIs
Account APIs
Parameter Management APIs
Monitoring Management APIs
Instance Management APIs
Backup and Restoration APIs
Data Types
Error Codes
FAQs
Product
Account Login
Features
Performance
Backup
Ops
Disk Overuse
IO Metric Exception
General References
Standards and Certification
Main Specification Performance Description
Performance Comparison Data for Strong Sync
Glossary

IO Metric Exception

PDF
Focus Mode
Font Size
Last updated: 2024-01-11 15:21:58

Exception

Log in to the TencentDB for MariaDB console and click an instance ID to enter the instance management page. On the Monitoring and Alarms tab, you can view two IO metrics.
Metric
Category
Description
IOUsageRate
Instance monitoring
Maximum IO utilization of the primary node
IOUsageRateNode
Node monitoring
IO utilization
In actual use, the above two IO metrics may increase abnormally even during off-peak hours. Alarms configured for them, if any, will be triggered.

Exception causes

Possible causes of the abnormal IO increase include:
There is a calculation problem with the IO metrics, and the actually displayed values are IO values of the server where the instance and node reside.
The IO levels of other instances on the same server increase, which may affect the IO monitoring of the current instance.

Solution

This issue involves alarms. We have located it and are fixing it. You can try the following workarounds for the time being:
Do not configure alarms for these two IO metrics. Or, increase their alarm thresholds to avoid the impact of abnormal alarms.
Ignore these two IO metrics when they increase abnormally and don't match the business usage.
We are monitoring and handling the IO usage issue uniformly to ensure the normal operations of instances.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback