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
On this page

Show all

Help Center/ TaurusDB/ Troubleshooting/ Connection Issues/ Description of Each IP Address

Description of Each IP Address

Updated on 2024-12-30 GMT+08:00

If you create a TaurusDB instance with one primary node and one read replica, there are up to five different IP addresses.

NOTE:

If you connect your application to a node of the DB instance through a private IP address for read and the node becomes faulty, the IP address cannot be accessed before the fault is rectified.

  1. Private IP address for read of the primary node (not recommended)

    After a DB instance is created, the system assigns a private IP address for read to the primary node. If your applications are deployed on a server that is in the same VPC as the DB instance, you can use the IP address to connect to the instance for read and write operations. But if a failover occurs and the primary node becomes a read replica, the IP address can only be used for read operations.

  2. Private IP address for read of a read replica (not recommended).

    After a DB instance is created, the system assigns a private IP address to the read replica. If your applications are deployed on a server that is in the same VPC as the DB instance, you can use this IP address to connect to the instance for read operations. But if a failover occurs and the read replica is promoted to primary, the IP address can be used for read and write operations.

  3. Private IP address

    After a DB instance is created, the system assigns a private IP address to the primary node. If your applications are deployed on a server that is in the same VPC as the DB instance, you can use the IP address to connect to the instance for read and write operations. But this IP address is always bound to the primary node. If a failover occurs, the IP address is reassigned to the new primary node, and can then still be used for read and write operations.

  4. Public IP address (EIP)

    After you buy a DB instance, you can bind an EIP to the instance to enable public accessibility, but can also unbind it later if needed. Just like a private IP address, an EIP is always bound to the primary node for read and write operations.

    Figure 1 Viewing the EIP and database port

  5. Proxy address

    After you buy a DB instance, you can enable database proxy and create a proxy instance. Then, the system assigns an IP address to the proxy instance. The proxy instance sends write requests to the primary node and read requests to the read replica based on the IP address, offloading the pressure on the primary node. Currently, read/write splitting IP addresses can only be used for intranet access.

NOTE:

Failover

By default, a TaurusDB instance contains at least two nodes, one primary node (read/write node) and one read replica (read-only node). You can create multiple read replicas if needed.

If the primary node becomes faulty, the system promotes a read replica to primary and demotes the primary node to read replica status.

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