TencentDB for MariaDB
- Release Notes and Announcements
- Announcements
- Product Introduction
- Getting Started
- Operation Guide
- Instance Management
- Account Management
- Backup and Rollback
- Migrating Data
- Database Sync(Legacy)
- Security Management
- CAM
- Monitoring and Alarms
- Practical Tutorial
- Security White Paper
- Development Guide
- API Documentation
- Making API Requests
- Security Group APIs
- Other APIs
- Account APIs
- Parameter Management APIs
- Monitoring Management APIs
- Instance Management APIs
- Backup and Restoration APIs
- General References
Instance Architecture
Last updated: 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 |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No