A high-availability system of influxdb with dual master architecture

Abstract

The invention discloses an InfluxDB high-availability system with a dual-master architecture, which belongs to the field of computer databases. The technical problem to be solved by the invention is how to ensure data consistency, avoid data loss, and seamlessly perform failover. The technical solution adopted is: the system includes an access module and a monitoring disaster recovery module. The access module and the monitoring disaster recovery module are used in conjunction with two InfluxDB nodes. The access module is used to execute the user's write request on the two InfluxDB nodes at the same time. Ensure the real-time consistency of the database nodes, and at the same time, the access module sends the user's read requests to the two InfluxDB nodes alternately to achieve load balancing and improve query performance; the monitoring disaster recovery module is used to monitor the availability status of the back-end InfluxDB nodes, and send The access module provides a status query interface, and at the same time automatically completes the data when the database data is found to be delayed.

Description

technical field [0001] The invention relates to the field of computer databases, in particular to an InfluxDB high-availability system with a dual-master architecture. Background technique [0002] As one of the most commonly used open source time-series databases on the market, InfluxDB has always lacked a relatively complete open source high-availability solution. Existing solutions usually use timing master-slave synchronization to achieve hot backup of data, and switch to the slave node for use when the master node fails. Since time-series databases are usually written very frequently, it is difficult to achieve seamless switching when a failure occurs, and the use of timing synchronization may also result in the loss of some data during switching. [0003] Therefore, how to ensure data consistency, avoid data loss, and seamlessly perform failover has become a problem that needs to be further solved in the InfluxDB high availability solution. [0004] Patent No. CN1106...

AI Technical Summary

Problems solved by technology

However, this technical solution is based on the master-slave architecture. The slave node and the master node adopt timing synchronization to maintain the final consistency. In the interval between two synchronizations, the data will have certain differences, and data may be lost during switching. In addition, the cluster has only one node at the same time. Nodes provide services and cannot perform load balancing

Images