Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ TaurusDB/ User Guide/ RegionlessDB Clusters (OBT)/ What Is a RegionlessDB Cluster?

What Is a RegionlessDB Cluster?

Updated on 2025-02-12 GMT+08:00

A RegionlessDB cluster consists of multiple TaurusDB instances in different regions around the world. Currently, a RegionlessDB cluster consists of one primary instance (in the primary region) and up to five standby instances (in standby regions). Data is synchronized between primary and standby instances, providing nearby access and regional DR capabilities.

Figure 1 RegionlessDB cluster principle

Scenarios

  • Remote multi-active deployment

    Data is synchronized among instances in a RegionlessDB cluster. For lower network latency and quicker resource access, you can select the instance nearest to your workloads.

  • Remote disaster recovery

    If there is a region-level fault on the primary instance, workloads can be switched to a standby instance for remote DR.

Architecture

Figure 2 Architecture
  • Cross-region deployment is supported. Redo logs generated in the primary instance are synchronized to a standby instance and written to DFV storage. Pages required for database access are replayed. For details, see Figure 2. (Data is synchronized based on the replication node Source of the primary instance and the replication node Target of the standby instance.)
  • In the primary instance, the read replica obtains required redo logs and pages from DFV storage through the primary node. In the standby instance, the read replica obtains required redo logs and pages from DFV storage through the replication node Target.

Advantages

  • Global deployment and nearby data access

    Instances in a RegionlessDB cluster are from different regions around the world. Data generated by the primary instance can be directly read from the nearest standby instance.

  • Low latency of cross-region replication

    Redo logs are directly and uninterruptedly read from the DFV storage for asynchronous replication. The replication latency is less than 1 second thanks to high-throughput parallel data synchronization.

  • No downtime for the primary node during data synchronization

    The replication node of the primary instance reads data from different nodes in the DFV storage in parallel for synchronization. This means that the primary node does not need to directly synchronize data to the standby instances. Instead, it only needs to update the location information of redo logs in the storage to the replication node of the primary instance. In this way, workloads on the primary node are not affected.

  • Too many read replicas

    There are up to five standby instances in a cluster, and each standby instance supports up to 15 read replicas.

    NOTE:

    When you are creating a DB instance, a maximum of 10 read replicas can be created at a time.

  • Region-level disaster recovery

    If there is a region-level fault on the primary instance, workloads can be quickly switched to a standby instance for remote DR, achieving an RPO in minutes and an RTO in seconds.

    NOTE:
    • To use region-level disaster recovery, submit a service ticket.
    • Recovery Point Objective (RPO): the maximum data loss amount tolerated by the system.
    • Recovery Time Objective (RTO): the maximum service interruption duration tolerated by the system. It refers to the requirement for the recovery duration of an information system failure or service function failure caused by a disaster.

Constraints

  • Only pay-per-use instances can be created.
  • The kernel version must be 2.0.46.231000 or later, and the primary instance must be a new instance. For details about how to check the kernel version, see How Can I Check the Version of a TaurusDB Instance?
  • The instances in a RegionlessDB cluster cannot use 192.168.0.0/16 as their subnet CIDR block.
  • The subnet CIDR blocks of the primary and standby instances in different regions must be different.
  • When a standby instance is created, data needs to be synchronized from the primary instance. The time required depends on how much data there is.
  • The primary instance in a RegionlessDB cluster cannot be restored to the original instance, and other instances cannot be restored to any instance in a RegionlessDB cluster.
  • If you have created proxy instances or HTAP instances for a TaurusDB instance, the TaurusDB instance cannot be used as an instance in a RegionlessDB cluster. To use it, delete the proxy instances or HTAP instances first.
  • The primary instance does not support the following operations:
    • Changing a database port
    • Changing a private IP address
    • Creating an HTAP instance
    • Creating a proxy instance
  • The standby instance does not support the following operations:
    • Resetting a password
    • Creating and restoring a backup
    • Creating an account
    • Authorizing an account
    • Creating a proxy instance
    • Creating an HTAP instance
    • Promoting a read replica to the primary node
    • Changing a database port
    • Changing a private IP address
    • Modifying auto scaling policies
  • Data across regions is synchronized through a network. The VPN bandwidth must be greater than the write bandwidth of the primary instance in a RegionlessDB cluster.
  • In large-scale DDL scenarios, the replication latency may fluctuate for more than 1 second.
  • RegionlessDB clusters do not support OpenAPIs.
  • A RegionlessDB cluster consists of one primary instance (in the primary region) and up to five standby instances (in standby regions). The primary instance processes both read and write requests, while the standby instances only process read requests. Table 1 lists the maximum specifications supported by a RegionlessDB cluster.
    Table 1 Specifications

    Description

    Primary Instance

    Standby Instance

    Max. Instances

    1

    5

    Max. Read/Write Nodes per Instance

    1

    0

    Max. Read-only Nodes per Instance

    15

    15

    NOTE:

    When you are creating a DB instance, a maximum of 10 read replicas can be created at a time.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback