Announcements

Alarm Upgrade

Product Introduction

Overview

Strengths

Use Cases

Regions and AZs

InnoDB engine

Purchase Guide

Billing Overview (InnoDB)

Product Pricing (InnoDB)

Purchase and Upgrade

Refund

Payment Overdue

Backup Space Billing

Getting Started

InnoDB Engine

Operation Guide（InnoDB）

Instance Management

Disaster Recovery Read-Only Instance

Changing Networks

Account Management

Security Management

Slow Query Analysis

Backup and Rollback

Data Migration

Database Audit

Practical Tutorial

Import from Standalone Instance to TDSQL Instance

Import Between TDSQL Instances

Selection of TDSQL Instance and Shard Configuration

Security White Paper

Platform Security Design

Tenant Security Features

Development Guide

InnoDB

API Documentation

History

Introduction

API Category

Security Group APIs

Other APIs

Making API Requests

TDSQL APIs

Data Types

Error Codes

FAQs

InnoDB

General References

Performance Comparison Data for Strong Sync

Glossary

Instance Architecture

PDF

フォーカスモード

フォントサイズ

最終更新日: 2024-01-06 17:31:28

InnoDB engine
Note: 
As the database audit feature is being refactored and upgraded, it is not available for newly purchased instances during this period.
Instance Architecture
Definition
Node
Feature
Standard Edition (one source and one replica)
Each shard provides a high-availability architecture based on source/replica active-active deployment.
Two nodes: One source node and one replica node
Supports read-only replicas.
﻿
In the 1-source-1-replica architecture, the read-only replica feature can only be used for low-load read-only tasks. Avoid high-load tasks such as large transactions, as they affect the backup tasks and availability of the replica server.
﻿
Automatic node failover.
Default sampling granularity for monitoring: Once every 5 minutes.
Maximum backup time: 7 days.
Operation log backup time: 7 days.
Supports database audit where audit logs can be retained for 15 days and an unlimited number of rules which can be configured.
﻿
Standard Edition (one source and two replicas)
Each shard provides a high-availability architecture based on source/replica multi-site active-active deployment.
Three nodes: One source node and two replica nodes
Finance Edition (one source and one replica)
Each shard provides a high-availability architecture based on source/replica active-active deployment.
Two nodes: One source node and one replica node
Supports other deployment schemes. To use other schemes, contact your Tencent Cloud sale rep.
Supports read-only replicas and implements intelligent load scheduling for read-only replicas.
Automatic node failover.
Default sampling granularity for monitoring: Once every 1 minute.
Maximum backup time: 3,650 days. You need to submit a ticket for application.
Operation log backup time: 60 days by default (1 year for archive storage).
Supports database audit where audit logs can be retained for 15 days.
Provides assistance for regulatory compliance.
﻿
Finance Edition (one source and two replicas)
Each shard provides a high-availability architecture based on source/replica multi-site active-active deployment.
Three nodes: One source node and two replica nodes
TDStore engine
In the beta test phase, the TDStore engine adopts a high-availability architecture of three nodes: one source node and two replica nodes.

ヘルプとサポート

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

営業担当者にお問い合わせいただくかチケットを提出してサポートを求めることができます。

フィードバック

tencent cloud

TDSQL for MySQL

Instance Architecture

InnoDB engine

TDStore engine

ヘルプとサポート

Instance Architecture	Definition	Node	Feature
Standard Edition (one source and one replica)	Each shard provides a high-availability architecture based on source/replica active-active deployment.	Two nodes: One source node and one replica node	Supports read-only replicas. In the 1-source-1-replica architecture, the read-only replica feature can only be used for low-load read-only tasks. Avoid high-load tasks such as large transactions, as they affect the backup tasks and availability of the replica server. Automatic node failover. Default sampling granularity for monitoring: Once every 5 minutes. Maximum backup time: 7 days. Operation log backup time: 7 days. Supports database audit where audit logs can be retained for 15 days and an unlimited number of rules which can be configured.
	Standard Edition (one source and two replicas)	Each shard provides a high-availability architecture based on source/replica multi-site active-active deployment.		Three nodes: One source node and two replica nodes
Finance Edition (one source and one replica)	Each shard provides a high-availability architecture based on source/replica active-active deployment.	Two nodes: One source node and one replica node	Supports other deployment schemes. To use other schemes, contact your Tencent Cloud sale rep. Supports read-only replicas and implements intelligent load scheduling for read-only replicas. Automatic node failover. Default sampling granularity for monitoring: Once every 1 minute. Maximum backup time: 3,650 days. You need to submit a ticket for application. Operation log backup time: 60 days by default (1 year for archive storage). Supports database audit where audit logs can be retained for 15 days. Provides assistance for regulatory compliance.
	Finance Edition (one source and two replicas)	Each shard provides a high-availability architecture based on source/replica multi-site active-active deployment.		Three nodes: One source node and two replica nodes