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

Ops

PDF
フォーカスモード
フォントサイズ
最終更新日: 2024-01-11 15:21:58

I have purchased a CVM instance in East China (Shanghai Zone 2) and a TencentDB for MariaDB instance in Shanghai, and both of them are in the basic network. Why is the TencentDB for MariaDB instance unpingable on the CVM instance?

TencentDB disables the ping operation by default. You can use Telnet to check connectivity if needed.

What can I do if Navicat MySQL 8.0.x of TencentDB for MariaDB has a connection error?

Please use the latest version for connection.

What thread is binlog dump of TencentDB for MariaDB?

It is a normal master/slave sync thread, which is resident.

What can I do if an error occurs when I use the multi-thread download tool Axel to download TencentDB for MariaDB backup or log files?

Multi-thread download is not supported. You can use the wget --content-disposition command for download.

Why does the master/slave delay of TencentDB for MariaDB suddenly increase even to several minutes?

The TencentDB Console supports most common database parameters and sets security thresholds for them. If a parameter to be modified does not exist or cannot be modified to a specific value, please submit a ticket for assistance.

What can I do if an error occurs when I run SELECT INTO OUTFILE or ./mysqldump on a TencentDB for MariaDB instance to export files locally?

Files cannot be written to instance server directories.

Why does an error similar to "READ ONLY" occur when I run SELECT FOR UPDATE on a TencentDB for MariaDB instance?

Some SQL statements do not support read/write separation. SELECT FOR UPDATE is a write operation and will cause an error.

A large number of slow queries or performance problems occur shortly after I migrate data to TencentDB for MariaDB. How do I troubleshoot them?

You can enter the instance details page in the TencentDB for MariaDB Console and select "Performance Optimization" > "Slow Query Analysis" to specifically analyze the slow queries. Possible reasons include:
If connection failed, it may be because that a large number of slow queries previously affected the performance, and now TencentDB for MariaDB uses the thread pool mechanism to control the number of active threads, so the connection cannot be established.
Data was just migrated to the TencentDB for MariaDB instance and has not been fully cached to the memory; therefore, part of the data needs to be pulled from the disk with longer consumption time, leading to a drop in performance.

How do I troubleshoot the XA_RBTIMEOUT error on a TencentDB for MariaDB instance?

It is possible that a large transaction has generated a super-large binlog. You are recommended to add an auto-increment field to the required tables.



ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック