HomeMogDBMogDB StackUqbar
v2.1

Documentation:v2.1

Supported Versions:

Other Versions:

Ultimate RTO

Availability

This feature is available since MogDB 1.1.0.

Introduction

  • The database host can be quickly restored after being restarted.
  • Logs can be synchronized between the primary and standby nodes to accelerate playback on the standby node.

Benefits

When the service load is heavy, the playback speed of the standby node cannot catch up with that of the primary node. After the system runs for a long time, logs are accumulated on the standby node. If a host is faulty, data restoration takes a long time and the database is unavailable, which severely affects system availability.

The ultimate recovery time object (RTO) is enabled to reduce the data recovery time after a host fault occurs and improve availability.

Description

After the ultimate RTO function is enabled, multi-level pipelines are established for Xlog log playback to improve the concurrency and log playback speed.

Enhancements

None

Constraints

The ultimate RTO focuses only on whether the RTO of the standby node meets the requirements. The ultimate RTO has the flow control effect. Therefore, you do not need to enable the flow control function. This feature does not support the read operation on the standby node. If you query the standby node, a core dump may occur on the standby node. This feature does not apply to the primary/standby/secondary scenario. In primary/standby/secondary deployment mode (that is, replication_type is set to 0), the database cannot be started.

Dependencies

None

Copyright © 2011-2024 www.enmotech.com All rights reserved.