Hierarchical-database high-availability system based on guard model

Abstract

The invention discloses a hierarchical-database high availability system based on a guard model. The system comprises a client terminal, a guard unit, a driving unit and a database cluster, wherein the client terminal interacts with the driving unit through configuring guard node information for the guard unit so as to access the database cluster. The guard unit can provide the client terminal with service, and meanwhile monitor the survival status of a main database and a secondary database in real time. If the main database fails, automatic switchover of a main database trouble is achieved, and differential data is compensated during the switchover process, thereby ensuring that no data is lost when the main database fails. The driving unit receives the guard node information transmitted by the client terminal, analyzes the information, and returns the analyzed information to the main database and then to the client terminal. The database cluster is a hierarchical database master-slave replication cluster. Based on a guard idea, through combining hierarchical database features to improve the traditional guard idea, the system not only can achieve automatic switchover of the main database trouble, but also can ensure that no data is lost at the same time, thereby guaranteeing availability and integrity of service to the utmost extent.

Description

technical field [0001] The invention belongs to the technical field of hierarchical databases, and in particular relates to a high-availability system of hierarchical databases based on a sentinel model. Background technique [0002] The hierarchical database is a high-performance database based on the LSM algorithm, and the data is stored on the hard disk according to different levels. The database supports master-slave replication architecture, which is divided into master database nodes and slave database nodes. The master database generates incremental logs in real time, and the slave database synchronizes the master database incremental logs in real time. The current position of the incremental logs is called the synchronization offset; The data on the master database that is not synchronized to the slave database is called differential data, which can be obtained through the interface of the hierarchical database itself; in general, the synchronization offsets of the m...

AI Technical Summary

Problems solved by technology

[0009] 2) Manual processing is complex

[0010] Once the main database is down, manual processing is required, including selecting a new main database, compensating for difference data, restoring the new cluster, and modifying the client configuration. The operation steps are complex and time-consuming

[0011] 3) Data loss

[0016] 1) The main database failure cannot be automatically switched

[0017] Once the main library fails, manual intervention is required, and automatic failover cannot be achieved, and the availability is relatively low

[0018] 2) Complicated operation

[0021] The virtual IP service itself has high availability problems, which increases maintenance costs. If the virtual IP service is unstable, it will also affect the availability of the database

[0022] 4) Data loss

[0023] When the main library is down, the data that has not been synchronized to the slave library will be lost

Images