CN117149905B - Time sequence data copying method and device - Google Patents
Time sequence data copying method and device Download PDFInfo
- Publication number
- CN117149905B CN117149905B CN202311029203.9A CN202311029203A CN117149905B CN 117149905 B CN117149905 B CN 117149905B CN 202311029203 A CN202311029203 A CN 202311029203A CN 117149905 B CN117149905 B CN 117149905B
- Authority
- CN
- China
- Prior art keywords
- node
- protocol
- data
- standby
- sent
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 22
- 230000010076 replication Effects 0.000 claims description 6
- 230000005540 biological transmission Effects 0.000 claims description 3
- 238000004891 communication Methods 0.000 claims description 3
- 238000005516 engineering process Methods 0.000 claims description 3
- 230000008569 process Effects 0.000 claims description 2
- 238000011084 recovery Methods 0.000 abstract 1
- 238000006467 substitution reaction Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/163—In-band adaptation of TCP data exchange; In-band control procedures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
- G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
-
- 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/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2474—Sequence data queries, e.g. querying versioned data
-
- 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
- G06F16/275—Synchronous replication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/03—Protocol definition or specification
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Data Mining & Analysis (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Probability & Statistics with Applications (AREA)
- Software Systems (AREA)
- Computational Linguistics (AREA)
- Fuzzy Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to the technical field of time sequence databases, in particular to a time sequence data copying method and a time sequence data copying device. Compared with the prior art, the invention realizes the incremental synchronization of the data by judging the number of the data rows in each table in the time sequence database, synchronizes the data to a new time sequence database, reduces the backup of redundant data and improves the high-availability disaster recovery capability of the database.
Description
Technical Field
The invention relates to the technical field of time sequence databases, and particularly provides a time sequence data copying method and device.
Background
The time sequence database is a database specially used for storing and processing time sequence data, and supports functions of high-efficiency reading and writing, high-compression storage, interpolation, aggregation and the like of the time sequence data. Time series data tends to be large in data size and the requirement for data consistency is not high, and typically strong consistency of data is not required.
The data stored in the database is important to the user. When the database is abnormal and can not be used continuously. This results in a loss of data which is unacceptable to the user. So how to reasonably backup the data of the database is a problem to be solved by those skilled in the art.
Disclosure of Invention
The invention aims at the defects of the prior art and provides a time sequence data copying method with strong practicability.
The invention further aims to provide a time sequence data copying device which is reasonable in design, safe and applicable.
The technical scheme adopted for solving the technical problems is as follows:
A time sequence data copying method uses TCP network communication technology to define multiple data protocol types based on time sequence database, and realizes the synchronization of time sequence data by transmitting data from a main node to a standby node through the mode of data log and then rewriting the data log into a table by the standby node through the mutual transmission of different data protocols.
Further, the data protocol types include:
Rep_db: the master node sends a message to the slave node to tell the slave node to start copying, and simultaneously, the names of libraries to be copied and the names of all tables in the libraries are sent to the slave node;
op_table: the backup node informs the master node to acquire the metadata of the target table according to the library name and the table name sent by the master node, and the master node sends the metadata of the table required by the backup node to the backup node after receiving the protocol;
Resp_field_list: the method comprises the steps that a master node sends metadata required by a standby node to the standby node, and then the standby node creates a corresponding table according to the metadata sent by the master node after receiving a protocol;
Get_table: the standby node requests specific data in the table from the main node, the main node inquires out the data log in the table after receiving the protocol, and then the data log is sent to the standby node.
Further, the data protocol types further include:
Cmd_obj: the master node sends a protocol before the data log to tell the standby node that the data log is to be sent next, the standby node receives the protocol, starts to receive the data log, and rewrites the data into the table according to the data log until the termination protocol is received;
TABLE_DATA: the master node sends a data log to the slave node, and after the slave node receives the protocol, the slave node analyzes the protocol according to the format of metadata, and then rewrites the content of the data log into a table;
Cmd_eof: after all the data logs are sent to the standby node, the main node sends the protocol, and the standby node does not accept the data logs after receiving the protocol.
Further, the specific flow is as follows:
s1, a master node sends REP_DB protocol;
S2, the standby node analyzes the REP_DB protocol and sends an OP_TABLE protocol to the main node;
S3, the master node analyzes the OP_TABLE protocol and sends the RESP_FIELD_LIST protocol to the standby node;
S4, the standby node analyzes the RESP_FIELD_LIST protocol;
S5, after receiving the REP_DB command, the standby node creates a copied task and adds the copied task into a task queue for queuing;
S6, each time a task thread is executed, taking out a task from the task queue for execution, and sending a GET_TABLE protocol;
S7, the master node analyzes the GET_TABLE protocol to read out the DATA log, sends the DATA log to the standby node through a plurality of TABLE_DATA protocols, and then sends the CMD_EOF protocol to inform the standby node that the DATA log is sent completely;
s8, after receiving the CMD_OBJ protocol sent by the master node, the standby node receives the TABLE_DATA protocol and rewrites the DATA to the standby node.
Further, in step S1, the master node transmits a rep_db protocol in which names of all tables under a library to be copied are transmitted to the slave node, and the rep_db protocol is at a library level, each library transmitting the rep_db protocol;
in step S2, the standby node obtains the names of the TABLEs to be copied sent from the master node by parsing the rep_db protocol, and then sends an op_table protocol to the master node for each TABLE.
Further, in step S3, the master node queries metadata of a TABLE wanted by the slave node by parsing the op_table protocol, and sends the metadata to the slave node through the resp_field_list protocol;
In step S4, the standby node obtains metadata of the table sent by the master node by parsing the resp_field_list protocol, and after obtaining, the standby node queries whether the table exists or not;
if so, the data in the table is recorded, and if not, a new table is created.
Further, in step S5, after receiving the rep_db command, the standby node creates a replicated task, and adds the replicated task to a task queue for queuing;
In step S6, each time a task thread is executed, a task is taken out from the task queue and executed, the get_table protocol is sent according to the related information in the task, and the standby node sends the number of data lines in the TABLE of the standby node to the master node.
Further, in step S7, the master node obtains the number of rows of the TABLE of the slave node by parsing the get_table protocol, and the master node reads the DATA log after the number of rows, and sends the cmd_obj protocol to tell the slave node to send the DATA log of the TABLE next, and then sends the DATA log to the slave node through multiple table_data protocols;
After the data log is sent, the master node sends CMD_EOF protocol again to inform the standby node that the data log is sent completely;
In step S8, after receiving the cmd_obj protocol sent from the master node, the slave node starts to continuously receive the table_data protocol, and rewrites the DATA to the slave node by parsing the DATA log sent in the table_data protocol until the slave node receives the cmd_eof protocol, and the TABLE replication process ends.
A time-series data copying apparatus comprising: at least one memory and at least one processor;
The at least one memory for storing a machine readable program;
The at least one processor is configured to invoke the machine-readable program to perform a time-series data replication method.
Compared with the prior art, the time sequence data copying method and device have the following outstanding beneficial effects:
In the time sequence database, the increment synchronization of the data is realized by judging the number of the data rows in each table, the data is synchronized to a new time sequence database, the backup of redundant data is reduced, and the high-availability disaster tolerance capability of the database is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a method of copying time series data.
Detailed Description
In order to provide a better understanding of the aspects of the present invention, the present invention will be described in further detail with reference to specific embodiments. It will be apparent that the described embodiments are only some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
A preferred embodiment is given below:
As shown in fig. 1, in one time-series data replication method in this embodiment, based on a time-series database, a TCP network communication technology is used to define multiple data protocol types, and synchronization of time-series data is implemented by transmitting data from a master node to a slave node through a data log mode through mutual transmission of different data protocols, and then the slave node rewrites the data log into a table.
Wherein, the data protocol type includes:
rep_db: the master node sends a message to the slave node telling the slave node to start replication, and at the same time sends the names of the libraries to be replicated and the names of all tables in the libraries to the slave node.
Op_table: and the standby node informs the main node to acquire the metadata of the target table according to the library name and the table name sent by the main node, and the main node sends the metadata of the table required by the standby node to the standby node after receiving the protocol.
Resp_field_list: the master node sends the metadata wanted by the standby node to the standby node, and then the standby node creates a corresponding table according to the metadata sent by the master node after receiving the protocol.
Get_table: the standby node requests specific data in the table from the main node, the main node inquires out the data log in the table after receiving the protocol, and then the data log is sent to the standby node.
Cmd_obj: the master node sends a protocol before the data log to tell the standby node that the data log is to be sent next, the standby node receives the protocol, starts to receive the data log, and rewrites the data into the table according to the data log until the termination protocol is received.
TABLE_DATA: the master node sends the data log to the slave node, and after the slave node receives the protocol, the slave node analyzes the protocol according to the format of the metadata, and then rewrites the content of the data log into the table.
Cmd_eof: after all the data logs are sent to the standby node, the main node sends the protocol, and the standby node does not accept the data logs after receiving the protocol.
The specific operation flow is as follows:
S1, a master node sends a REP_DB protocol, names of all tables under libraries to be copied are sent to a standby node in the REP_DB protocol, the REP_DB protocol is of a library level, and each library is required to send one REP_DB protocol.
S2, the standby node acquires the names of the TABLEs to be copied sent by the main node by analyzing the REP_DB protocol, and then sends an OP_TABLE protocol to the main node for each TABLE.
S3, the master node inquires the metadata of the TABLE wanted by the slave node by analyzing the OP_TABLE protocol, and sends the metadata to the slave node by the RESP_FIELD_LIST protocol.
S4, the standby node obtains the metadata of the table sent by the main node by analyzing the RESP_FIELD_LIST protocol, and after obtaining, the standby node inquires whether the table exists or not;
if so, the data in the table is recorded, and if not, a new table is created.
S5, after receiving the REP_DB command, the standby node creates a copied task and adds the copied task into a task queue for queuing.
S6, each time a task thread is executed, taking out a task from the task queue and executing the task. The get_table protocol is sent according to the related information in the task, and the standby node sends the data line number in the standby node list to the master node.
S7, the master node acquires the number of lines of the TABLE of the slave node by analyzing the GET_TABLE protocol, the master node reads out the DATA log after the number of lines, firstly transmits the CMD_OBJ protocol to tell the slave node to transmit the DATA log of the TABLE next, and then transmits the DATA log to the slave node through a plurality of TABLE_DATA protocols.
And after the data log is sent, the master node sends the CMD_EOF protocol again to inform the standby node that the data log is sent completely.
S8, after receiving the CMD_OBJ protocol sent by the main node, the standby node starts to continuously receive the TABLE_DATA protocol, and rewrites the DATA to the standby node by analyzing the DATA log sent in the TABLE_DATA protocol until the standby node receives the CMD_EOF protocol, and the copying flow of the TABLE is ended.
Based on the above method, a time-series data copying apparatus in this embodiment includes: at least one memory and at least one processor;
The at least one memory for storing a machine readable program;
The at least one processor is configured to invoke the machine-readable program to perform a time-series data replication method.
The above-mentioned specific embodiments are merely specific examples of the present invention, and the scope of the present invention is not limited to the specific embodiments, and any suitable changes or substitutions made by those skilled in the art, which conform to the technical solutions described in the claims of the present invention, should fall within the scope of the present invention.
Although embodiments of the present invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made therein without departing from the principles and spirit of the invention, the scope of which is defined in the appended claims and their equivalents.
Claims (6)
1. A time sequence data copying method is characterized in that a TCP network communication technology is used on the basis of a time sequence database to define a plurality of data protocol types, data is transmitted from a main node to a standby node through the mode of a data log through the mutual transmission of different data protocols, and the standby node rewrites the data log into a table to realize the synchronization of time sequence data;
the data protocol types include:
Rep_db: the master node sends a message to the slave node to tell the slave node to start copying, and simultaneously, the names of libraries to be copied and the names of all tables in the libraries are sent to the slave node;
op_table: the backup node informs the master node to acquire the metadata of the target table according to the library name and the table name sent by the master node, and the master node sends the metadata of the table required by the backup node to the backup node after receiving the protocol;
Resp_field_list: the method comprises the steps that a master node sends metadata required by a standby node to the standby node, and then the standby node creates a corresponding table according to the metadata sent by the master node after receiving a protocol;
get_table: the standby node requests specific data in the table from the main node, the main node inquires out a data log in the table after receiving the protocol, and then the data log is sent to the standby node;
the data protocol types further include:
Cmd_obj: the master node sends a protocol before the data log to tell the standby node that the data log is to be sent next, the standby node receives the protocol, starts to receive the data log, and rewrites the data into the table according to the data log until the termination protocol is received;
TABLE_DATA: the master node sends a data log to the slave node, and after the slave node receives the protocol, the slave node analyzes the protocol according to the format of metadata, and then rewrites the content of the data log into a table;
cmd_eof: after all the data logs are sent to the standby node, the main node sends the protocol, and the standby node does not accept the data logs after receiving the protocol;
The specific flow is as follows:
s1, a master node sends REP_DB protocol;
S2, the standby node analyzes the REP_DB protocol and sends an OP_TABLE protocol to the main node;
S3, the master node analyzes the OP_TABLE protocol and sends the RESP_FIELD_LIST protocol to the standby node;
S4, the standby node analyzes the RESP_FIELD_LIST protocol;
S5, after receiving the REP_DB command, the standby node creates a copied task and adds the copied task into a task queue for queuing;
S6, each time a task thread is executed, taking out a task from the task queue for execution, and sending a GET_TABLE protocol;
S7, the master node analyzes the GET_TABLE protocol to read out the DATA log, sends the DATA log to the standby node through a plurality of TABLE_DATA protocols, and then sends the CMD_EOF protocol to inform the standby node that the DATA log is sent completely;
s8, after receiving the CMD_OBJ protocol sent by the master node, the standby node receives the TABLE_DATA protocol and rewrites the DATA to the standby node.
2. A time series data copying method according to claim 1, wherein in step S1, the master node transmits a rep_db protocol in which names of all tables under a library to be copied are transmitted to the backup node, and the rep_db protocol is library-level, each library transmitting the rep_db protocol;
in step S2, the standby node obtains the names of the TABLEs to be copied sent from the master node by parsing the rep_db protocol, and then sends an op_table protocol to the master node for each TABLE.
3. The method according to claim 1, wherein in step S3, the master node queries the metadata of the TABLE desired by the slave node by parsing the op_table protocol, and sends the metadata to the slave node by means of the resp_field_list protocol;
In step S4, the standby node obtains metadata of the table sent by the master node by parsing the resp_field_list protocol, and after obtaining, the standby node queries whether the table exists or not;
if so, the data in the table is recorded, and if not, a new table is created.
4. A method of copying time series data according to claim 3, wherein in step S5, the standby node creates a copied task after receiving the rep_db command, and adds the task to the task queue for queuing;
In step S6, each time a task thread is executed, a task is taken out from the task queue and executed, the get_table protocol is sent according to the related information in the task, and the standby node sends the number of data lines in the TABLE of the standby node to the master node.
5. The method for copying time series DATA according to claim 4, wherein in step S7, the master node obtains the number of rows of the TABLE of the slave node by parsing the get_table protocol, the master node reads the DATA log after the number of rows, and first transmits the cmd_obj protocol to tell the slave node to transmit the DATA log of the TABLE next, and then transmits the DATA log to the slave node through a plurality of table_data protocols;
After the data log is sent, the master node sends CMD_EOF protocol again to inform the standby node that the data log is sent completely;
In step S8, after receiving the cmd_obj protocol sent from the master node, the slave node starts to continuously receive the table_data protocol, and rewrites the DATA to the slave node by parsing the DATA log sent in the table_data protocol until the slave node receives the cmd_eof protocol, and the TABLE replication process ends.
6. A time-series data copying apparatus, comprising: at least one memory and at least one processor;
The at least one memory for storing a machine readable program;
The at least one processor being configured to invoke the machine readable program to perform the method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311029203.9A CN117149905B (en) | 2023-08-16 | 2023-08-16 | Time sequence data copying method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311029203.9A CN117149905B (en) | 2023-08-16 | 2023-08-16 | Time sequence data copying method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117149905A CN117149905A (en) | 2023-12-01 |
| CN117149905B true CN117149905B (en) | 2024-05-24 |
Family
ID=88901843
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311029203.9A Active CN117149905B (en) | 2023-08-16 | 2023-08-16 | Time sequence data copying method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117149905B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007075587A2 (en) * | 2005-12-19 | 2007-07-05 | Commvault Systems, Inc. | Systems and methods for performing data replication |
| CN104679604A (en) * | 2015-02-12 | 2015-06-03 | 大唐移动通信设备有限公司 | Method and device for switching between master node and standby node |
| WO2018014650A1 (en) * | 2016-07-20 | 2018-01-25 | 华为技术有限公司 | Distributed database data synchronisation method, related apparatus and system |
| CN108090222A (en) * | 2018-01-05 | 2018-05-29 | 中国科学院计算技术研究所 | A kind of data-base cluster internodal data synchronization system |
| CN112597251A (en) * | 2020-12-29 | 2021-04-02 | 天津南大通用数据技术股份有限公司 | Database cluster log synchronization method and device, server and storage medium |
| CN113987064A (en) * | 2021-09-23 | 2022-01-28 | 阿里云计算有限公司 | Data processing method, system and equipment |
| CN114722092A (en) * | 2022-03-10 | 2022-07-08 | 阿里云计算有限公司 | Time series data processing method, system, storage medium and electronic equipment |
-
2023
- 2023-08-16 CN CN202311029203.9A patent/CN117149905B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007075587A2 (en) * | 2005-12-19 | 2007-07-05 | Commvault Systems, Inc. | Systems and methods for performing data replication |
| CN104679604A (en) * | 2015-02-12 | 2015-06-03 | 大唐移动通信设备有限公司 | Method and device for switching between master node and standby node |
| WO2018014650A1 (en) * | 2016-07-20 | 2018-01-25 | 华为技术有限公司 | Distributed database data synchronisation method, related apparatus and system |
| CN108090222A (en) * | 2018-01-05 | 2018-05-29 | 中国科学院计算技术研究所 | A kind of data-base cluster internodal data synchronization system |
| CN112597251A (en) * | 2020-12-29 | 2021-04-02 | 天津南大通用数据技术股份有限公司 | Database cluster log synchronization method and device, server and storage medium |
| CN113987064A (en) * | 2021-09-23 | 2022-01-28 | 阿里云计算有限公司 | Data processing method, system and equipment |
| CN114722092A (en) * | 2022-03-10 | 2022-07-08 | 阿里云计算有限公司 | Time series data processing method, system, storage medium and electronic equipment |
Non-Patent Citations (2)
| Title |
|---|
| 分布式文件系统元数据服务器高可用性设计;战科宇;李小勇;刘海涛;;小型微型计算机系统;20130415(04);全文 * |
| 集群数据库系统的日志复制和故障恢复;王嘉豪;蔡鹏;钱卫宁;周傲英;;软件学报;20170331(03);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117149905A (en) | 2023-12-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109739929B (en) | Data synchronization method, device and system | |
| CN104951474B (en) | Method and device for acquiring MySQL binlog incremental log | |
| EP3258396A1 (en) | Data synchronization method, device and system | |
| CN110377577B (en) | Data synchronization method, device, system and computer readable storage medium | |
| CN110601903B (en) | Data processing method and device based on message queue middleware | |
| CN113987064A (en) | Data processing method, system and equipment | |
| US11640261B2 (en) | Log processing method to avoid log collision, and related device and system | |
| CN113704359A (en) | Synchronization method, system and server for multiple data copies of time sequence database | |
| CN117149905B (en) | Time sequence data copying method and device | |
| CN113905054B (en) | RDMA (remote direct memory access) -based Kudu cluster data synchronization method, device and system | |
| CN113946287B (en) | Distributed storage system, data processing method thereof and related device | |
| CN114595288A (en) | SQL command level-based multi-IDC distributed system data synchronization method | |
| CN113032477B (en) | GTID-based long-distance data synchronization method, device and computing equipment | |
| CN111241200B (en) | Master-slave synchronous processing method and device based on SQLite database | |
| WO2024179139A1 (en) | Data synchronization method, database, data synchronization apparatus, and product | |
| CN116501700B (en) | APP formatted file offline storage method, device, equipment and storage medium | |
| CN115210694A (en) | Data transmission method and device | |
| CN112328560A (en) | File scheduling method and system | |
| CN111831954A (en) | Content data updating method and device, computer equipment and storage medium | |
| CN116302605A (en) | Message engine-based message transmission method | |
| CN116186082A (en) | Data summarizing method based on distribution, first server and electronic equipment | |
| CN115834604A (en) | Data transmitting terminal, data receiving terminal, synchronization method and computer program product | |
| CN113868146A (en) | Test task generation method and device, electronic equipment and storage medium | |
| CN112199329A (en) | Double-machine operation and maintenance data filing and cleaning method and equipment based on fortress machine | |
| CN118051563B (en) | Disaster recovery method based on isomorphic clusters of distributed database |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |