Deployment Solutions

The openGauss can be deployed in standalone mode or with one primary node and multiple standby nodes.

Common Concepts

  • Standalone

    Standalone deployment indicates that there is only one database instance.

  • HA

    In an HA cluster, primary and standby DB instances exist in the system. The primary DB instance supports read and write, and the standby DB instance supports read-only.

  • One primary and multiple standbys

    One primary and multiple standbys refer to the system that has one primary node and multiple standby nodes. A maximum of four standby nodes are supported.

  • Hot/Cold backup

    Cold backup: There is only a simple backup set that cannot provide services.

    Hot backup: Backup clusters can provide services for external systems.

Deployment Modes

For details about the standalone and HA cluster deployment modes, see Table 1.

Table 1 Deployment modes in openGauss

Deployment Mode

Technical Solution

HA

Basic Configuration Requirement

Business Scenario

Characteristics

Technical Specifications

Standalone

Standalone

HA is not supported.

Single equipment room

Physical machine (PM)

  • No reliability and availability requirements for the system.
  • Used for trial use and commissioning.
  • RTO and RPO are uncontrollable.
  • Instance-level DR is not supported. The system is unavailable when instance faults occur.
  • Lost instance data cannot be restored.

Primary/Standby

Primary node + Standby node

Instance faults can be withstood.

Single equipment room

PM

  • No network latency between nodes.
  • Instance faults in the cluster can be withstood.
  • Applicable to scenarios without high reliability requirements.
  • RPO=0
  • Instance fault RTO < 10s
  • AZ-level DR is not supported.
  • Recommended maximum availability mode

One primary and multiple standbys

Primary node + Multiple standby nodes +Quorum

Instance faults can be withstood.

Single equipment room

PM

  • No network latency between nodes.
  • Instance faults in the cluster can be withstood.
  • RPO=0
  • Instance fault RTO < 10s
  • AZ-level DR is not supported.
  • Primary/Standby synchronization is recommended.
  • At least two copies and at most four copies are supported.

Hardware and Software Specifications

openGauss supports the following CPUs and OSs:

Table 2 openGauss software and hardware specifications

Delivery Mode

CPU

OS

Open source and offline

X86

CentOS 7.6

Kunpeng

openEuler 20.03 LTS

Introduction to Deployment Solutions

The overall deployment solution can be classified into three types: standalone deployment, primary/standby deployment, and one-primary and multiple-standby deployment. For details, see the following sections.

  • Standalone Deployment

    The standalone deployment does not ensure reliability or availability. There is only one data copy. If data is damaged or lost, data can be restored only through physical backup. Therefore, this deployment mode applies to scenarios such as experiencing databases and commissioning syntax functions in the test environment. You are not advised to use this mode on the commercial live network.

    Figure 1 Standalone deployment

  • Primary/Standby Deployment

    The primary/standby deployment mode is equivalent to two data copies. The primary and standby nodes each have a data copy. The standby node receives and plays back logs.

    Figure 2 Primary/Standby deployment

  • Deployment with One Primary and Multiple Standbys

    The multi-copy deployment mode provides the capability of defending against instance-level faults. This mode is applicable to scenarios where equipment room DR is not required but some hardware faults need to be prevented.

    Generally, the one-primary and two-standby mode is used for multi-copy deployment. There are three copies in total. The reliability of the three copies is 99.99%, which can meet the reliability requirements of most applications.

    • In primary/standby DN quorum replication, data is synchronized to at least one standby to ensure the maximum performance.
    • If any of primary and standby DNs is faulty, services will not be affected.
    • There are three copies of data. If one node is faulty, the system still has two copies of data. In addition, any standby DN can be promoted to primary.
    • The primary and standby instances cannot be deployed on the same physical machine.

    Figure 3 One-primary and multiple-standby deployment

Feedback
编组 3备份
    openGauss 2024-05-25 00:42:51
    cancel