CN114579671A - Inter-cluster data synchronization method and device - Google Patents
Inter-cluster data synchronization method and device Download PDFInfo
- Publication number
- CN114579671A CN114579671A CN202210496191.XA CN202210496191A CN114579671A CN 114579671 A CN114579671 A CN 114579671A CN 202210496191 A CN202210496191 A CN 202210496191A CN 114579671 A CN114579671 A CN 114579671A
- Authority
- CN
- China
- Prior art keywords
- cluster
- synchronized
- data
- synchronization
- transaction log
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/178—Techniques for file synchronisation in file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
Abstract
The application relates to a method and a device for synchronizing data among clusters, wherein the method for synchronizing the data among the clusters comprises the steps that cluster synchronization services are arranged in each cluster, and all the cluster synchronization services are connected with a cluster database; and collecting transaction logs generated by each cluster, wherein the transaction logs comprise service data needing to be synchronized and cluster nodes needing to be synchronized, and the cluster database receives the transaction logs and synchronizes the service data needing to be synchronized to the cluster nodes needing to be synchronized. According to the method and the device, data among clusters are synchronized through the cluster synchronization service and the cluster database, file transmission copying is not needed, the main and standby nodes can read and write in the data, the synchronization efficiency is improved, data of all cluster nodes are guaranteed to be consistent, the cluster nodes needing synchronization are distinguished by the identification, the log transmission amount is reduced, and the log transmission efficiency is improved.
Description
Technical Field
The application belongs to the technical field of computers, and particularly relates to a method and a device for data synchronization between clusters.
Background
With the increasing demand for data management and storage, in order to meet the requirement for large-scale data storage and management, a scheme for managing and storing data by building a server cluster appears in recent years. Multiple clusters are usually configured to acquire data from the same data source for storage and management. In the prior art, data synchronization between clusters is performed by Streaming Replication (WAL log transfer), a PG cluster is provided with a main cluster and a standby cluster, and once the main cluster generates a log, the log is immediately transferred to the standby cluster. Because the WAL logs can only be transmitted one by one, the standby cluster is at least one WAL log behind the main cluster, and the situation of inconsistent or discontinuous data between the main cluster and the standby cluster occurs, so that the user experience is influenced. And only the master cluster generates the WAL log, the backup cluster only reads, the writable node is the master node, and the cluster use efficiency is not high. In the prior art, synchronous stream replication among PG clusters needs to run a process for receiving WAL logs for each node, and each node needs to transmit the WAL logs during stream replication, so that the copy quantity is large and the efficiency is low.
Disclosure of Invention
In order to overcome the problems that the traditional inter-cluster data synchronization method has inconsistent or discontinuous data between a main cluster and a standby cluster, the cluster use efficiency is not high, the copy quantity is large, and the efficiency is low to at least a certain extent, the application provides a method and a device for synchronizing the data between the clusters.
In a first aspect, the present application provides a method for synchronizing data between clusters, including:
each cluster is provided with cluster synchronization service, and all the cluster synchronization services are connected with a cluster database;
collecting transaction logs generated by each cluster, wherein the transaction logs comprise service data needing to be synchronized and cluster nodes needing to be synchronized;
and the cluster database receives the transaction log and synchronizes the service data needing to be synchronized to the cluster nodes needing to be synchronized.
Further, synchronizing the service data to be synchronized to the cluster node to be synchronized includes:
judging whether the state of the cluster nodes needing to be synchronized is normal or not;
if so, the cluster database synchronizes data to the cluster nodes in a normal state;
otherwise, caching the transaction log, and performing data synchronization when the cluster node state is recovered to be normal.
Further, the method also comprises the following steps:
and performing compression and/or encryption operation on the transaction log.
Further, the method also comprises the following steps:
generating a timestamp corresponding to a transaction log when the transaction log is generated;
comparing the data stamp of the current transaction log to be synchronized with the time stamp of the actual transaction log corresponding to the current transaction log to be synchronized in the cluster;
and carrying out synchronous operation on the transaction log corresponding to the latest timestamp.
Further, the method also comprises the following steps:
NTP is used for time synchronization of cluster nodes.
Further, the data synchronization after the cluster node status returns to normal includes:
judging whether the cluster node state is recovered to be normal or not;
and if so, redoing the transaction log needing redoing.
Further, the method also comprises the following steps:
judging whether the data synchronization task is executed successfully;
if not, the transaction log which fails in synchronization is cached for a preset period and then is redone.
Further, the method also comprises the following steps:
and creating synchronous service processes, wherein one synchronous service process only processes synchronous operation of one transaction log.
In a second aspect, the present application provides an inter-cluster data synchronization apparatus, including:
the cluster synchronization service module is used for setting cluster synchronization service in each cluster, and all the cluster synchronization services are connected with the cluster database;
the unified transaction log generation module is used for collecting transaction logs of all clusters, wherein the transaction logs comprise service data needing to be synchronized and cluster nodes needing to be synchronized;
and the synchronization module is used for receiving the transaction log by the cluster database and synchronizing the service data needing to be synchronized to the cluster nodes needing to be synchronized.
Further, the method also comprises the following steps:
and the cluster state monitoring module is used for judging whether the cluster node state is normal or not.
The technical scheme provided by the embodiment of the application can have the following beneficial effects:
according to the method and the device for data synchronization among the clusters, the cluster synchronization service is arranged in each cluster, and all the cluster synchronization services are connected with the cluster database; the method comprises the steps of collecting transaction logs generated by each cluster, wherein the transaction logs comprise service data needing to be synchronized and cluster nodes needing to be synchronized, receiving the transaction logs by a cluster database, synchronizing the service data needing to be synchronized to the cluster nodes needing to be synchronized, synchronizing data among the clusters by a cluster synchronization service and the cluster database, and not needing file transmission copying, wherein main and standby nodes can read and write the data, so that the synchronization efficiency is improved, the data consistency of each cluster node is ensured, and the cluster nodes needing to be synchronized are identified and distinguished, so that the log transmission amount is reduced, and the log transmission efficiency is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
Fig. 1 is a flowchart of a method for synchronizing data between clusters according to an embodiment of the present application.
Fig. 2 is a flowchart of a method for synchronizing data between clusters according to another embodiment of the present application.
Fig. 3 is a functional structure diagram of an inter-cluster data synchronization apparatus according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail below. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the examples given herein without making any creative effort, shall fall within the protection scope of the present application.
Fig. 1 is a flowchart of an inter-cluster data synchronization method according to an embodiment of the present application, and as shown in fig. 1, the inter-cluster data synchronization method includes:
s11: each cluster is provided with cluster synchronization service, and all the cluster synchronization services are connected with a cluster database;
s12: collecting transaction logs generated by each cluster, wherein the transaction logs comprise service data needing to be synchronized and cluster nodes needing to be synchronized;
s13: and the cluster database receives the transaction log and synchronizes the service data needing to be synchronized to the cluster nodes needing to be synchronized.
The traditional data synchronization among clusters is carried out in a way of transferring WAL logs by stream replication, a main cluster and a standby cluster are arranged in a PG cluster, and the main cluster and the standby cluster can be immediately transferred as long as the main cluster generates the logs. Because the WAL logs can only be transmitted one by one, the standby cluster is at least one WAL log behind the main cluster, and the condition of inconsistent or discontinuous data between the standby cluster and the main cluster can occur, so that the user experience is influenced. And only the master cluster generates the WAL log, the backup cluster only reads, the writable node is the master node, and the cluster use efficiency is not high. In the prior art, synchronous stream replication among PG clusters requires that each node needs to run a process for receiving WAL logs, and each node needs to transmit the WAL logs during stream replication, so that the copy quantity is large and the efficiency is low.
In the embodiment, the cluster synchronization service is set in each cluster, and all the cluster synchronization services are connected with the cluster database; the method comprises the steps of collecting transaction logs generated by each cluster, wherein the transaction logs comprise service data needing to be synchronized and cluster nodes needing to be synchronized, receiving the transaction logs by a cluster database, synchronizing the service data needing to be synchronized to the cluster nodes needing to be synchronized, synchronizing data among the clusters by a cluster synchronization service and the cluster database, and not needing file transmission copying, wherein main and standby nodes can read and write the data, so that the synchronization efficiency is improved, the data consistency of each cluster node is ensured, and the cluster nodes needing to be synchronized are identified and distinguished, so that the log transmission amount is reduced, and the log transmission efficiency is improved.
Fig. 2 is a flowchart of an inter-cluster data synchronization method according to another embodiment of the present application, and as shown in fig. 2, the inter-cluster data synchronization method includes:
s201: collecting transaction logs generated by each cluster, wherein the transaction logs comprise service data needing to be synchronized and cluster nodes needing to be synchronized;
s202: the transaction log is subject to compression and/or encryption operations.
The storage space of the transaction log can be reduced by compressing the transaction log; encrypting the transaction log may protect data security.
S203: each cluster is provided with cluster synchronization service, and all the cluster synchronization services are connected with a cluster database;
s204: the cluster database receives the transaction log and judges whether the state of the cluster nodes needing to be synchronized is normal, if so, S205 is executed, otherwise, S206 is executed;
s205: the cluster database synchronizes data to the cluster nodes in a normal state;
s206: and caching the transaction log, and performing data synchronization when the cluster node state is recovered to be normal.
In some embodiments, performing data synchronization when the cluster node state returns to normal includes:
judging whether the cluster node state is recovered to be normal or not;
and if so, redoing the transaction log needing redoing.
In some embodiments, further comprising: NTP is used for time synchronization for cluster nodes.
Generating a timestamp corresponding to a transaction log when the transaction log is generated;
comparing the data stamp of the transaction log to be synchronized with the time stamp of the actual transaction log corresponding to the transaction log to be synchronized in the cluster;
and carrying out synchronous operation on the transaction log corresponding to the latest timestamp.
The cluster nodes use NTP for time synchronization, and the transaction logs use timestamps to ensure the integrity of the transactions.
In some embodiments, further comprising: judging whether the data synchronization task is successfully executed;
if not, the transaction log which fails in synchronization is cached for a preset period and then is redone.
In some embodiments, further comprising:
and creating synchronous service processes, wherein one synchronous service process only processes synchronous operation of one transaction log.
The pg stream replication process further includes:
wal sender: the wal sender exists in the main library, and the wal sender process transmits wal between the latest LSN of the main library and the latest LSN of the standby library to the standby library;
wal receiver: wal receiver exists in stock. The wal receiver process passes the latest LSN number of the standby library to the master library. Receiving WAL data transmitted by the WAL sender by the WAL receiver and writing the WAL data into a WAL log;
startup: and the backup library instance recovers the process. Wal logs are replayed on the standby library.
In some embodiments, further comprising:
and setting the cluster state, wherein when the cluster state is set to be a maintenance state, the cluster enters the maintenance state, and the cluster can perform system patch upgrading operation in the maintenance state.
The inter-cluster data synchronization method provided in this embodiment is illustrated as follows:
suppose that a service cluster has four clusters of A, B, C and D, and the clusters A, B, C and D simultaneously generate service data, such as account opening, account cancellation and customer information modification data. The data generated by the cluster can identify the data source, for example, the data generated by the cluster A is marked with a mark data (A), the data generated by the cluster B is marked with a mark data (B), and so on, the data (C) and the data (D);
the clusters A, B, C and D are all provided with cluster synchronization services, namely SYN (A), SYN (B), SYN (C) and SYN (D), and the synchronization services SYN are directly connected with a cluster database for operation.
The cluster A, B, C and D is provided with failure REDO service REDO (A), REDO (B), REDO (C) and REDO (D), and the failure REDO service REDO is directly connected with the cluster database for operation.
The modification data (A) generated by the A cluster, such as account opening, account selling, customer information and the like, needs to be synchronized to the B, C, D cluster, the same data (B) needs to be synchronized with the A, C, D cluster, and the like.
If the state of the cluster B is abnormal in the process of synchronizing the data (A) to the B, C, D cluster, the cluster database synchronizes the data to the C, D cluster with a normal state, the data state is modified to be data (A, C, D) after synchronization is completed, when the cluster B returns to be normal, the data is subjected to redo (A) redo service operation, since the A, C, D cluster state is data (A, C, D), data synchronization is completed, and at the moment, the redo (A) service only performs data synchronization on the cluster B, so that invalid copying is avoided.
And, the data (a) synchronization process is syn (a) service direct operation cluster database, and writes into the cluster database through database write operation without transferring data (a) file to B, C, D cluster, reducing the file transfer process.
In the embodiment, the cluster nodes use NTP for time synchronization, the transaction logs use timestamps to ensure the integrity of transactions, data synchronization among clusters only has no file transmission copy, different nodes are directly connected through cluster synchronization service and written into different clusters, the cluster nodes needing synchronization are distinguished by using operation marks in the transaction logs in the data synchronization among the clusters, the main node and the standby node can be read and written, more nodes can be written into the clusters, and the efficiency is higher.
An embodiment of the present invention provides an inter-cluster data synchronization apparatus, such as the functional structure diagram shown in fig. 3, where the inter-cluster data synchronization apparatus includes:
a cluster synchronization service module 31, configured to set a cluster synchronization service in each cluster, where all the cluster synchronization services are connected to a cluster database;
a unified transaction log generating module 32, configured to collect transaction logs of each cluster, where the transaction logs include service data to be synchronized and cluster nodes to be synchronized;
and a synchronization module 33, configured to receive the transaction log by the cluster database, and synchronize the service data to be synchronized to the cluster node to be synchronized.
In some embodiments, further comprising:
and the cluster state monitoring module 34 is configured to determine whether the cluster node state is normal.
In this embodiment, a cluster synchronization service module is used to set cluster synchronization services in each cluster, all the cluster synchronization services are connected to a cluster database, a unified transaction log generation module collects transaction logs of each cluster, each transaction log includes service data to be synchronized and cluster nodes to be synchronized, a synchronization module synchronizes the service data to be synchronized to the cluster nodes to be synchronized, data among the clusters are synchronized through the cluster synchronization service and the cluster database, file transfer copying is not needed, the master node and the slave node can both read and write data, synchronization efficiency is improved, data consistency of each cluster node is ensured, and the cluster nodes to be synchronized are identified, log transmission amount is reduced, and log transmission efficiency is improved.
It is understood that the same or similar parts in the above embodiments may be mutually referred to, and the same or similar parts in other embodiments may be referred to for the content which is not described in detail in some embodiments.
It should be noted that, in the description of the present application, the terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Further, in the description of the present application, the meaning of "a plurality" means at least two unless otherwise specified.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and the scope of the preferred embodiments of the present application includes other implementations in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional component mode. The integrated module, if implemented in the form of a software functional component and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
In the description herein, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
While embodiments of the present application have been shown and described above, it will be understood that the above embodiments are exemplary and should not be construed as limiting the present application and that changes, modifications, substitutions and alterations in the above embodiments may be made by those of ordinary skill in the art within the scope of the present application.
It should be noted that the present invention is not limited to the above-mentioned preferred embodiments, and those skilled in the art can obtain other products in various forms without departing from the spirit of the present invention, but any changes in shape or structure can be made within the scope of the present invention with the same or similar technical solutions as those of the present invention.
Claims (10)
1. An inter-cluster data synchronization method, comprising:
each cluster is provided with cluster synchronization service, and all the cluster synchronization services are connected with a cluster database;
collecting transaction logs generated by each cluster, wherein the transaction logs comprise service data needing to be synchronized and cluster nodes needing to be synchronized;
and the cluster database receives the transaction log and synchronizes the service data needing to be synchronized to the cluster nodes needing to be synchronized.
2. The method according to claim 1, wherein the synchronizing the service data to be synchronized to the cluster node to be synchronized comprises:
judging whether the state of the cluster nodes needing to be synchronized is normal or not;
if so, the cluster database synchronizes data to the cluster nodes in a normal state;
otherwise, caching the transaction log, and performing data synchronization when the cluster node state is recovered to be normal.
3. The inter-cluster data synchronization method according to claim 1 or 2, further comprising:
and performing compression and/or encryption operation on the transaction log.
4. The inter-cluster data synchronization method according to claim 1 or 2, further comprising:
generating a timestamp corresponding to a transaction log when the transaction log is generated;
comparing the data stamp of the current transaction log to be synchronized with the time stamp of the actual transaction log corresponding to the current transaction log to be synchronized in the cluster;
and carrying out synchronous operation on the transaction log corresponding to the latest timestamp.
5. The inter-cluster data synchronization method of claim 4, further comprising:
NTP is used for time synchronization of cluster nodes.
6. The method according to claim 2, wherein the data synchronization is performed when the state of the cluster node returns to normal, and the method comprises:
judging whether the cluster node state is recovered to be normal or not;
and if so, redoing the transaction log needing redoing.
7. The method of claim 1, further comprising:
judging whether the data synchronization task is successfully executed;
if not, the transaction log which fails in synchronization is cached for a preset period and then is redone.
8. The method of claim 1, further comprising:
and creating synchronous service processes, wherein one synchronous service process only processes synchronous operation of one transaction log.
9. An inter-cluster data synchronization apparatus, comprising:
the cluster synchronization service module is used for setting cluster synchronization service in each cluster, and all the cluster synchronization services are connected with the cluster database;
the unified transaction log generation module is used for collecting transaction logs of all clusters, wherein the transaction logs comprise service data needing to be synchronized and cluster nodes needing to be synchronized;
and the synchronization module is used for receiving the transaction log by the cluster database and synchronizing the service data needing to be synchronized to the cluster nodes needing to be synchronized.
10. The inter-cluster data synchronization apparatus according to claim 9, further comprising:
and the cluster state monitoring module is used for judging whether the cluster node state is normal or not.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210496191.XA CN114579671A (en) | 2022-05-09 | 2022-05-09 | Inter-cluster data synchronization method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210496191.XA CN114579671A (en) | 2022-05-09 | 2022-05-09 | Inter-cluster data synchronization method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114579671A true CN114579671A (en) | 2022-06-03 |
Family
ID=81769023
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210496191.XA Pending CN114579671A (en) | 2022-05-09 | 2022-05-09 | Inter-cluster data synchronization method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114579671A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115544172A (en) * | 2022-11-28 | 2022-12-30 | 杭州欧若数网科技有限公司 | Method and system for synchronizing data among clusters of one master and multiple slaves in real time |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102917072A (en) * | 2012-10-31 | 2013-02-06 | 北京奇虎科技有限公司 | Device, system and method for carrying out data migration between data server clusters |
| CN103198159A (en) * | 2013-04-27 | 2013-07-10 | 国家计算机网络与信息安全管理中心 | Transaction-redo-based multi-copy consistency maintaining method for heterogeneous clusters |
| US20150278039A1 (en) * | 2014-03-25 | 2015-10-01 | International Business Machines Corporation | Handling failed cluster members when replicating a database between clusters |
| CN106484565A (en) * | 2016-09-22 | 2017-03-08 | 华为数字技术（成都）有限公司 | Method of data synchronization between multiple data centers and relevant device |
| CN108090222A (en) * | 2018-01-05 | 2018-05-29 | 中国科学院计算技术研究所 | A kind of data-base cluster internodal data synchronization system |
| CN108123976A (en) * | 2016-11-30 | 2018-06-05 | 阿里巴巴集团控股有限公司 | Data back up method, apparatus and system between cluster |
| CN109960710A (en) * | 2019-01-16 | 2019-07-02 | 平安科技（深圳）有限公司 | Method of data synchronization and system between database |
| WO2019154394A1 (en) * | 2018-02-12 | 2019-08-15 | 中兴通讯股份有限公司 | Distributed database cluster system, data synchronization method and storage medium |
| CN112163038A (en) * | 2020-09-18 | 2021-01-01 | 中国建设银行股份有限公司 | Cross-cluster data synchronization method, device, equipment and storage medium |
| CN113377582A (en) * | 2021-08-16 | 2021-09-10 | 北京易鲸捷信息技术有限公司 | Distributed database disaster tolerance method based on log pushing |
-
2022
- 2022-05-09 CN CN202210496191.XA patent/CN114579671A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102917072A (en) * | 2012-10-31 | 2013-02-06 | 北京奇虎科技有限公司 | Device, system and method for carrying out data migration between data server clusters |
| CN103198159A (en) * | 2013-04-27 | 2013-07-10 | 国家计算机网络与信息安全管理中心 | Transaction-redo-based multi-copy consistency maintaining method for heterogeneous clusters |
| US20150278039A1 (en) * | 2014-03-25 | 2015-10-01 | International Business Machines Corporation | Handling failed cluster members when replicating a database between clusters |
| CN106484565A (en) * | 2016-09-22 | 2017-03-08 | 华为数字技术（成都）有限公司 | Method of data synchronization between multiple data centers and relevant device |
| CN108123976A (en) * | 2016-11-30 | 2018-06-05 | 阿里巴巴集团控股有限公司 | Data back up method, apparatus and system between cluster |
| CN108090222A (en) * | 2018-01-05 | 2018-05-29 | 中国科学院计算技术研究所 | A kind of data-base cluster internodal data synchronization system |
| WO2019154394A1 (en) * | 2018-02-12 | 2019-08-15 | 中兴通讯股份有限公司 | Distributed database cluster system, data synchronization method and storage medium |
| CN109960710A (en) * | 2019-01-16 | 2019-07-02 | 平安科技（深圳）有限公司 | Method of data synchronization and system between database |
| CN112163038A (en) * | 2020-09-18 | 2021-01-01 | 中国建设银行股份有限公司 | Cross-cluster data synchronization method, device, equipment and storage medium |
| CN113377582A (en) * | 2021-08-16 | 2021-09-10 | 北京易鲸捷信息技术有限公司 | Distributed database disaster tolerance method based on log pushing |
Non-Patent Citations (1)
| Title |
|---|
| 王建宣等: "基于HP_Unix+Oracle 10g RAC构建广东气象短信数据中心", 《计算机时代》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115544172A (en) * | 2022-11-28 | 2022-12-30 | 杭州欧若数网科技有限公司 | Method and system for synchronizing data among clusters of one master and multiple slaves in real time |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110209726B (en) | Distributed database cluster system, data synchronization method and storage medium | |
| US7793060B2 (en) | System method and circuit for differential mirroring of data | |
| US20060277384A1 (en) | Method and apparatus for auditing remote copy systems | |
| CN102968486B (en) | A kind of highly reliable file synchronisation method based on change journal | |
| CN100495354C (en) | Method and system for consolidating session information for a cluster of sessions in a coupled session environment | |
| JP2001356945A (en) | Data backup recovery system | |
| CN101594256A (en) | Disaster recovery method, device and system | |
| CN111597197B (en) | Data reconciliation method and device between databases, storage medium and electronic equipment | |
| CN109684410B (en) | System, method and storage medium for determining synchronization delay of master database and slave database | |
| CN105389231A (en) | Database dual-computer backup method and system | |
| CN114579671A (en) | Inter-cluster data synchronization method and device | |
| CN110209526A (en) | A kind of accumulation layer synchronization system and storage medium | |
| CN115878384A (en) | Distributed cluster based on backup disaster recovery system and construction method | |
| CN111966467A (en) | Method and device for disaster recovery based on kubernetes container platform | |
| CN113535665B (en) | Method and device for synchronizing log files between main database and standby database | |
| CN113190620B (en) | Method, device, equipment and storage medium for synchronizing data between Redis clusters | |
| WO2017122060A1 (en) | Parallel recovery for shared-disk databases | |
| CN108460163A (en) | K-DB method for synchronizing data of database, device, equipment and storage medium | |
| CN110489491B (en) | Full data synchronization device suitable for A/B network double clusters | |
| CN114741367B (en) | Data synchronization method, data synchronization device, electronic equipment, storage medium and program product | |
| WO2021189283A1 (en) | Method and device for data processing, electronic device, and storage medium | |
| CN105323271A (en) | Cloud computing system, and processing method and apparatus thereof | |
| CN113535430A (en) | Application data read-write separation method and device, computer equipment and storage medium | |
| CN114706714A (en) | Method for synchronizing computer memory division snapshots | |
| US7610459B2 (en) | Maintain owning application information of data for a data storage system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220603 |
|
| RJ01 | Rejection of invention patent application after publication |