This topic describes the performance differences before and after hot standby is enabled.

Comparison overview

The following table lists the performance differences between hot standby nodes (with the hot standby feature enabled) and read-only nodes:
Item Hot standby node Read-only node
Service capabilities Does not provide services Provides read-only services
Switchover (active O&M, such as minor version upgrade and cluster configuration changes) 5 seconds before transactions per second (TPS) drops to zero Over 10 seconds before TPS drops to zero
Failover (disaster recovery, such as recovering the primary node) 5 seconds before TPS drops to zero 60 seconds of service interruption
The preceding table indicates that:
  • In active O&M scenarios, read-only nodes with hot standby enabled experience shorter service interruption time.
  • In disaster recovery scenarios, read-only nodes with hot standby enabled have shorter service interruption time. In addition, services and transactions are not interrupted, and the number of errors reported by clients is significantly reduced.

Detailed information

The following section provides detailed information about failover speed before and after hot standby is enabled:

  • Switchover (active O&M, such as minor version upgrade and cluster configuration changes)
    • Normal read-only nodes (when hot standby and transaction resumable upload are disabled): over 10 seconds before TPS drops to zero Normal read-only nodes: active O&M scenarios
    • Hot standby nodes (when hot standby and transaction resumable upload are enabled): 5 seconds before TPS drops to zero Hot standby nodes: active O&M scenarios
  • Failover (disaster recovery, such as recovering the primary node)
    • Normal read-only nodes (when hot standby and transaction resumable upload are disabled): 60 seconds of service interruption Normal read-only nodes: disaster recovery scenarios
    • Hot standby nodes (when hot standby and transaction resumable upload are enabled): 5 seconds before TPS drops to zero Hot standby nodes: disaster recovery scenarios