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

Instance Architecture

PDF

포커스 모드

폰트 크기

마지막 업데이트 시간: 2024-01-11 15:21:58

Instance Architecture
Definition
Node
Feature
Standard Edition (one primary and one replica)
Each shard provides a high-availability architecture based on primary/replica active-active deployment.
Two nodes: One primary node and one replica node
Supports read-only replicas.
Note：
In the 1-primary-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: 30 days.
Operation log backup time: 60 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 primary and two replicas)
Each shard provides a high-availability architecture based on primary/replica multi-site active-active deployment.
Three nodes: One primary node and two replica nodes
Finance Edition (one primary and one replica)
Each shard provides a high-availability architecture based on primary/replica active-active deployment.
Two nodes: One primary 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 primary and two replicas)
Each shard provides a high-availability architecture based on primary/replica multi-site active-active deployment.
Three nodes: One primary node and two replica nodes
﻿

도움말 및 지원

문제 해결에 도움이 되었나요?

더 자세한 내용은 문의하기 또는 티겟 제출 을 통해 문의할 수 있습니다.

피드백

tencent cloud

TencentDB for MariaDB

Instance Architecture

도움말 및 지원

Instance Architecture	Definition	Node	Feature
Standard Edition (one primary and one replica)	Each shard provides a high-availability architecture based on primary/replica active-active deployment.	Two nodes: One primary node and one replica node	Supports read-only replicas. Note： In the 1-primary-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: 30 days. Operation log backup time: 60 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 primary and two replicas)	Each shard provides a high-availability architecture based on primary/replica multi-site active-active deployment.		Three nodes: One primary node and two replica nodes
Finance Edition (one primary and one replica)	Each shard provides a high-availability architecture based on primary/replica active-active deployment.	Two nodes: One primary 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 primary and two replicas)	Each shard provides a high-availability architecture based on primary/replica multi-site active-active deployment.		Three nodes: One primary node and two replica nodes