CN110647511A - Data synchronization method, computing device and computer storage medium - Google Patents
Data synchronization method, computing device and computer storage medium Download PDFInfo
- Publication number
- CN110647511A CN110647511A CN201910927251.7A CN201910927251A CN110647511A CN 110647511 A CN110647511 A CN 110647511A CN 201910927251 A CN201910927251 A CN 201910927251A CN 110647511 A CN110647511 A CN 110647511A
- Authority
- CN
- China
- Prior art keywords
- data
- write
- preset
- machine room
- synchronization
- 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/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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a data synchronization method, a computing device and a computer storage medium. The method comprises the following steps: packaging a data write-in request sent by a client by using a preset write-in command; calling a first write thread according to the data write-in request after encapsulation processing, and recording data write operation into a Redis cache region of a first machine room; calling a second write thread, writing data in the Redis cache region to a log file in a disk, and updating the file offset of the log file; calling a reading thread to read data writing operation in the log file based on a preset reading command containing file offset, and synchronizing the read data writing operation to a second machine room by utilizing a synchronous link established between the machine rooms; based on a preset synchronization command, data corresponding to the synchronized data writing operation is written into a Redis database of a second machine room, data synchronization is carried out between the two machine rooms based on log files, synchronization is not required to be carried out from the data every time, timely synchronization of the data is achieved, and resources are saved.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a data synchronization method, computing equipment and a computer storage medium.
Background
The Redis database is a memory type database, so the speed of reading data from the Redis database or writing data into the Redis database is very high, but the data is also a memory type database, log files cannot be recorded after the data is written into the Redis database, when data synchronization between machine rooms is performed in a machine room built by the conventional Redis database, a machine room special line needs to be built between the machine rooms firstly, then the data synchronization of the machine rooms is realized through the machine room special line, and in the data synchronization process, the machine room special line is likely to be disconnected due to various reasons, so that synchronization interruption is caused. After the reconnection recovery of the machine room dedicated line, data synchronization needs to be performed again because it is impossible to know which data are synchronized, that is, all data are synchronized again, so that resource waste is caused, and a serious delay phenomenon occurs when data in a plurality of Redis databases in one machine room need to be synchronized.
Disclosure of Invention
In view of the above, the present invention has been made to provide a data synchronization method, a computing device and a computer storage medium that overcome or at least partially solve the above-mentioned problems.
According to an aspect of the present invention, there is provided a data synchronization method, including:
packaging a data write-in request sent by a client by using a preset write-in command;
calling a first write thread according to the data write-in request after encapsulation processing, and recording data write operation into a Redis cache region of a first machine room; calling a second write thread, writing data in the Redis cache region to a log file in a disk, and updating the file offset of the log file;
calling a reading thread to read data writing operation in the log file based on a preset reading command containing file offset, and synchronizing the read data writing operation to a second machine room by utilizing a synchronous link established between the machine rooms;
and writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room based on the preset synchronization command.
According to another aspect of the present invention, there is provided a computing device comprising: the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is used for storing at least one executable instruction, and the executable instruction causes the processor to execute the following operations:
packaging a data write-in request sent by a client by using a preset write-in command;
calling a first write thread according to the data write-in request after encapsulation processing, and recording data write operation into a Redis cache region of a first machine room; calling a second write thread, writing data in the Redis cache region to a log file in a disk, and updating the file offset of the log file;
calling a reading thread to read data writing operation in the log file based on a preset reading command containing file offset, and synchronizing the read data writing operation to a second machine room by utilizing a synchronous link established between the machine rooms;
and writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room based on the preset synchronization command.
According to yet another aspect of the present invention, there is provided a computer storage medium having at least one executable instruction stored therein, the executable instruction causing a processor to:
packaging a data write-in request sent by a client by using a preset write-in command;
calling a first write thread according to the data write-in request after encapsulation processing, and recording data write operation into a Redis cache region of a first machine room; calling a second write thread, writing data in the Redis cache region to a log file in a disk, and updating the file offset of the log file;
calling a reading thread to read data writing operation in the log file based on a preset reading command containing file offset, and synchronizing the read data writing operation to a second machine room by utilizing a synchronous link established between the machine rooms;
and writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room based on the preset synchronization command.
According to the scheme provided by the invention, a preset write-in command is utilized to carry out encapsulation processing on a data write-in request sent by a client; calling a first write thread according to the data write-in request after encapsulation processing, and recording data write operation into a Redis cache region of a first machine room; calling a second write thread, writing data in the Redis cache region to a log file in a disk, and updating the file offset of the log file; calling a reading thread to read data writing operation in the log file based on a preset reading command containing file offset, and synchronizing the read data writing operation to a second machine room by utilizing a synchronous link established between the machine rooms; and writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room based on the preset synchronization command. Based on the scheme provided by the invention, two machine rooms built based on the Redis database can perform data synchronization through data writing operation recorded in the log file, so that the synchronization from the data is not required to be performed every time, the timely synchronization of the data is realized, the resources are saved, and the problem that the data synchronization cannot be performed based on the log file in the conventional scheme because the Redis database is a memory type database and the data is directly written into the Redis database without recording the log file is solved; in addition, the scheme realizes data synchronization by calling the first write thread, the second write thread and the read thread, thereby not only ensuring the advantage of high processing speed of the memory type database, but also improving the data synchronization efficiency.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 shows a flow diagram of a data synchronization method according to one embodiment of the invention;
FIG. 2 shows a schematic flow diagram of a data synchronization method according to another embodiment of the invention;
FIG. 3 shows a schematic structural diagram of a computing device according to one embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
Fig. 1 shows a flow diagram of a data synchronization method according to an embodiment of the invention. As shown in fig. 1, the method comprises the steps of:
and step S101, packaging the data writing request sent by the client by using a preset writing command.
Generally, operations performed by a client on a Redis database of a computer room are writing data and reading data, that is, writing data to the Redis database and reading data from the Redis database. In the prior art, when a data write request sent by a client is received, only an operation of writing data into a database is executed, and because an existing machine room built based on a Redis database does not have a concept of a log file, an operation of recording the data write operation into the log file is not executed. In order to realize data synchronization of a machine room built based on a Redis database, several Redis commands are newly added when the data synchronization is realized, wherein a preset write command is just one of the newly added commands.
Specifically, when a data write request sent by a client is received, a data write operation is not immediately performed according to the data write request, but the data write request is correspondingly processed, for example, a data write request sent by the client is encapsulated by using a preset write command. The preset write-in command is a command which is added for realizing the recording of data write operation into the log file, the data write-in request which is encapsulated by the preset write-in command is a new data write-in request, and the encapsulated data write-in request is endowed with other data processing requirements, such as the recording of the log file, besides the original data write-in requirement.
In this embodiment, the encapsulating process of the data write request sent by the client by using the preset write command may be to add a preset prefix, for example, WITHDQ, which is only illustrated here and has no limiting effect, and a person skilled in the art may set and add different prefixes according to actual requirements.
Step S102, calling a first write thread according to the data write-in request after encapsulation processing, and recording data write operation into a Redis cache region of a first machine room; and calling a second write thread, writing data in the Redis cache region to a log file in a disk, and updating the file offset of the log file.
After receiving the data write-in request after the encapsulation processing, analyzing the data write-in request after the encapsulation processing, so as to determine which data processing the data write-in request after the encapsulation processing requires, then performing corresponding data processing according to the data write-in request after the encapsulation processing, specifically, calling a first write thread, and recording the data write-in operation in the data write-in request into a Redis cache region (i.e., buff) of a first machine room; and calling a second write thread, writing data write operation in the Redis cache region to a log file in the disk, updating the file offset of the log file, and finishing the operation of recording the data write operation to the log file. Two write threads are selected for processing, so that the characteristic of high speed of the memory type database is reserved, and the characteristic of high speed of the memory type database is not sacrificed.
In this embodiment, each data write operation recorded in the log file corresponds to a file offset, each data write operation occupies a certain byte, and after the data write operation is landed on the log file in the magnetic disk, a certain space of the log file is occupied, and the occupied space corresponds to the byte occupied by the data write operation, so that the file offset of the log file can be updated according to the byte occupied by the data write operation. The file offset of the log file may monotonically increase as more and more data write operations are recorded.
Step S103, based on a preset read command containing file offset, calling a read thread to read data write operation in the log file, and synchronizing the read data write operation to a second machine room by using a synchronization link established between the machine rooms.
After the data writing operation is recorded in the log file, data synchronization can be executed, and in order to realize data synchronization of a machine room built based on a Redis database, a Redis command is additionally added: a preset read command, such as a DQSUB command, which is merely illustrative and not limiting, is based on which data write operations are read from the log file for data synchronization.
When reading data writing operation from the log file, a file offset is set, that is, a preset reading command carries the file offset, where the file offset is used to indicate that data writing operation needs to be performed from a position corresponding to the file offset in the log file. In this embodiment, based on a preset read command including a file offset, a read thread is separately invoked to read data write operations from a log file, specifically, the read thread first determines the data write operations corresponding to the file offset in the log file, then starts to read the data write operations from this point, and after the data write operations are read, synchronizes the read data write operations to a second machine room by using a synchronization link (e.g., TCP connection) established between the two machine rooms. For example, the read data write operation is set a 1; set b is 2; and setting a is 3, and the data writing operations are synchronized to the second computer room.
In the embodiment, the read thread is newly called to perform data synchronization, instead of performing data synchronization by using the first write thread or the second write thread, so that the original performance of the Redis database can be ensured, and data synchronization is realized under the condition that the original performance of the Redis database is ensured.
And step S104, writing the data corresponding to the synchronized data writing operation into a Redis database of the second machine room based on a preset synchronization command.
After the data writing operation is synchronized to the second computer room, the data corresponding to the synchronized data writing operation may be written into the Redis database of the second computer room, in steps S101-S102, the data writing operation recorded in the log file may be executed based on the data processing performed by the data writing request after being encapsulated by the preset writing command, however, when the data corresponding to the synchronized data writing operation is written into the Redis database of the second computer room, the operation of recording the log file is not desired to be executed, if the operation of recording the log file is always executed, an endless loop may be caused, which results in unnecessary waste of resources, and therefore, in the present embodiment, when the data is written into the Redis database of the second computer room, the data is based on another newly added Redis command: a preset synchronization command, for example, an APPLY command, which is only an example and does not have any limiting effect, requires the following data processing: and writing the data into the Redis database, but not executing the operation of recording the log file, namely, not recording the data writing operation into the log file corresponding to the second computer room. Specifically, after receiving the data write operation synchronized by the first computer room, based on a preset synchronization command, writing the data corresponding to the synchronized data write operation into the Redis database of the second computer room.
The log file in this embodiment records data write-in operation that the client directly writes in the local machine room, and the data synchronization is data synchronization between the two machine rooms, and the data synchronization is realized based on data write-in operation of the client to the first machine room, instead of data write-in operation of the client to the second machine room, and the synchronized data write-in operation is not recorded in the log file of the second machine room.
The data writing operation is recorded in the log file corresponding to the first machine room according to the sequence executed by the client, so that data writing is executed again according to the data writing operation, and the data in the Redis database of the second machine room can be ensured to be completely the same as the data in the Redis database of the first machine room.
According to the method provided by the embodiment of the invention, a preset write-in command is utilized to carry out encapsulation processing on a data write-in request sent by a client; calling a first write thread according to the data write-in request after encapsulation processing, and recording data write operation into a Redis cache region of a first machine room; calling a second write thread, writing data in the Redis cache region to a log file in a disk, and updating the file offset of the log file; calling a reading thread to read data writing operation in the log file based on a preset reading command containing file offset, and synchronizing the read data writing operation to a second machine room by utilizing a synchronous link established between the machine rooms; and writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room based on the preset synchronization command. Based on the scheme provided by the invention, two machine rooms built based on the Redis database can perform data synchronization through data writing operation recorded in the log file, so that the synchronization from the data is not required to be performed every time, the timely synchronization of the data is realized, the resources are saved, and the problem that the data synchronization cannot be performed based on the log file in the conventional scheme because the Redis database is a memory type database and the data is directly written into the Redis database without recording the log file is solved; in addition, the scheme realizes data synchronization by calling the first write thread, the second write thread and the read thread, thereby not only ensuring the advantage of high processing speed of the memory type database, but also improving the data synchronization efficiency.
Fig. 2 shows a flow diagram of a data synchronization method according to another embodiment of the present invention. As shown in fig. 2, the method comprises the steps of:
step S201, a preset write command is used to encapsulate a data write request sent by a client.
Step S202, calling a first write thread according to the data write-in request after encapsulation processing, recording data write-in operation into a Redis cache region of a first machine room, and writing data corresponding to the data write-in operation into a Redis database of the first machine room; and calling a second write thread, writing data in the Redis cache region to a log file in a disk, and updating the file offset of the log file.
The steps S201 and S202 in the embodiment shown in fig. 2 are similar to the steps S101 to S102 in the embodiment shown in fig. 1, and are not described in detail here.
And when the data writing request after the packaging processing also reserves the data processing required by the original data writing request when the data writing request is not packaged, calling a first writing thread according to the data writing request after the packaging processing, and writing the data corresponding to the data writing operation into a Redis database of a first computer room to realize the data writing required by the client. Wherein, the log file format is AOF format.
Step S203, based on the preset read command containing the file offset, calling a read thread to read the data write operation in the log file, and synchronizing the read data write operation to the second machine room by using the synchronization link established between the machine rooms.
The portion in step S203 in the embodiment shown in fig. 2 is similar to step S103 in the embodiment shown in fig. 1, and is not described in detail here.
Step S204, if the synchronization link established between the machine rooms is broken to cause synchronization failure, the synchronization operation is executed again from the breakpoint until the synchronization is successful.
In the data synchronization process, it is likely that a synchronization link established between the rooms is disconnected due to some reasons (for example, a link is unstable), and further synchronization fails, and in order to avoid a problem that data in a Redis database of a first room is inconsistent with data in a Redis database of a second room after data synchronization is caused by missing part of data write operation, a breakpoint resume mechanism is adopted in the embodiment, that is, synchronization operation is executed again from a breakpoint, and retry is performed continuously until data synchronization succeeds. After the synchronization fails, the embodiment does not need to acquire the full amount of data to perform data synchronization again, thereby saving the time required by synchronization. The log file is stored in the disk of the first computer room, so that the disk provides resource guarantee for multiple retries of breakpoint continuous transmission.
Step S205, detecting whether the file offset recorded in the second machine room is smaller than the file offset carried by the preset synchronization command, if so, executing step S206; if not, go to step S207.
In the case of breakpoint resume, there may be a case where the breakpoint is not very accurate, and therefore, before writing data into a Redis database of a second machine room, a file offset needs to be compared, where the file offset recorded in the second machine room is a file offset of a data writing operation corresponding to the data already written into the second machine room, and a file offset carried by a preset synchronization command is a file offset corresponding to a data writing operation after the data synchronization of this time, for example, the data synchronization of this time is a data writing operation between file offsets 120 and 150, then, the file offset carried by the preset synchronization command is 150, and this embodiment detects whether the file offset recorded in the second machine room is smaller than the file offset carried by the preset synchronization command, so as to determine whether the data corresponding to the data writing operation is written into the Redis database of the second machine room. The preset synchronization command comprises a machine room identifier and a file offset of the first machine room.
Step S206, writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room, and recording the file offset corresponding to the synchronized data writing operation and the computer room identifier of the first computer room.
When the file offset recorded in the second machine room is smaller than the file offset carried by the preset synchronization command, it indicates that the data is not written in the Redis database of the second machine room, and may perform an operation of writing the data corresponding to the synchronized data writing operation in the Redis database of the second machine room, specifically, the operation of writing the data corresponding to the data writing operation in the Redis database of the second machine room may be performed according to the file offset recorded in the second machine room, for example, the file offset recorded in the second machine room is 130, the file offset carried by the preset synchronization command is 150, and the operation of writing the data may be performed from the data writing operation corresponding to the file offset 131. And after the synchronization is finished, recording the file offset corresponding to the synchronized data writing operation and the machine room identifier of the first machine room.
Step S207, discarding the synchronized data writing operation, and waiting for the next data synchronization.
And under the condition that the file offset recorded in the second machine room is greater than or equal to the file offset carried by the preset synchronization command, the data is indicated to be written into a Redis database of the second machine room, the synchronized data writing operation can be discarded, and the next time of data synchronization is waited, so that data repetition can be avoided.
In this embodiment, if the synchronization link established between the computer rooms is normal, based on the preset synchronization command, the data corresponding to the synchronized data writing operation is written into the Redis database of the second computer room, and the file offset corresponding to the synchronized data writing operation and the computer room identifier of the first computer room are recorded.
Step S208, according to the preset deleting command including the file offset, deleting the data writing operation corresponding to the file offset in the log file of the first machine room.
Although the log file is stored in the disk of the first computer room, the disk space is also limited, in order to ensure that the disk can store more log files, after the data synchronization succeeds, deletion processing needs to be performed on the data write operation which has succeeded in the synchronization, and in order to implement the data write operation, a Redis command is additionally added: a preset deletion command, where the preset deletion command carries a file offset, where the file offset is used to indicate which data has been synchronized, which data write operations can be deleted, for example, all data write operations synchronized to a Redis database of a second machine room are deleted, after the synchronization is completed, the second machine room returns a notification message that the synchronization is successful to the first machine room, and the first machine room deletes, according to the notification message that the synchronization is successful, the data write operations in the log file of the first machine room based on the recorded file offset of the synchronized data write operations, for example, the file offset included in the preset deletion command is 100, and then deletes the data write operations corresponding to file offsets 1 to 100, which is only an example and does not have any limiting effect. This step is an optional step.
In step S209, if the first machine room is down or failed, the data service is switched to the second machine room.
In this embodiment, the first computer room is a main computer room and provides data service to the outside, and the second computer room is a standby computer room, and because data synchronization is performed between the first computer room and the second computer room in real time, if the first computer room is down or fails, the data service can be switched to the second computer room, and the second computer room provides data service to the outside, so that the normal use of the client is ensured.
In an optional implementation manner of the present invention, there may be a case where the first write thread and the second write thread access the Redis cache area of the first machine room at the same time, and for the case where the first write thread and the second write thread access the Redis cache area at the same time, contention between the two write threads may be solved based on an ATOMIC integrated circuit mechanism, and after it is determined that the first write thread or the second write thread accesses the Redis cache area of the first machine room, a spin lock is enabled, so that other threads cannot execute operations.
According to the method provided by the embodiment of the invention, two machine rooms built based on the Redis database can perform data synchronization through data writing operation recorded in the log file, so that the synchronization from the data is not needed to be performed every time, the timely synchronization of the data is realized, the resources are saved, and the problem that the data synchronization cannot be performed based on the log file in the existing scheme because the Redis database is a memory type database and the data is directly written into the Redis database without recording the log file is solved; in addition, the scheme realizes data synchronization by calling the first write thread, the second write thread and the read thread, thereby not only ensuring the advantage of high processing speed of the memory type database, but also improving the data synchronization efficiency; the data are ensured to be completely synchronized to the second machine room through breakpoint continuous transmission, and omission is avoided; after the breakpoint continuous transmission, detecting whether the file offset recorded by the second machine room is smaller than the file offset carried by the preset synchronization command, so that repeated execution of data synchronization can be avoided, and resources are saved; according to the preset deleting command containing the file offset, the data writing operation corresponding to the file offset in the log file of the first computer room is deleted, so that the disk can be guaranteed to have enough storage space for storing subsequent data writing operation, and data synchronization is carried out.
The embodiment of the invention also provides a nonvolatile computer storage medium, wherein the computer storage medium stores at least one executable instruction, and the computer executable instruction can execute the data synchronization method in any method embodiment.
The executable instructions may be specifically configured to cause the processor to:
packaging a data write-in request sent by a client by using a preset write-in command;
calling a first write thread according to the data write-in request after encapsulation processing, and recording data write operation into a Redis cache region of a first machine room; calling a second write thread, writing data in the Redis cache region to a log file in a disk, and updating the file offset of the log file;
calling a reading thread to read data writing operation in the log file based on a preset reading command containing file offset, and synchronizing the read data writing operation to a second machine room by utilizing a synchronous link established between the machine rooms;
and writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room based on the preset synchronization command.
In an optional implementation manner, the preset synchronization command includes a machine room identifier and a file offset of the first machine room;
the executable instructions further cause the processor to: and recording the file offset corresponding to the synchronized data writing operation and the machine room identifier of the first machine room.
In an alternative embodiment, the executable instructions further cause the processor to: and if the synchronization link established between the machine rooms is broken to cause synchronization failure, executing the synchronization operation again from the breakpoint until the synchronization is successful.
In an alternative embodiment, the executable instructions further cause the processor to:
detecting whether the file offset recorded by the second machine room is consistent with the file offset carried by the preset synchronous command or not;
if the file offset carried by the preset synchronization command is smaller than the file offset recorded by the second machine room, discarding the synchronized data writing operation;
and if the file offset carried by the preset synchronization command is larger than the file offset recorded by the second computer room, writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room.
In an alternative embodiment, the executable instructions further cause the processor to: and deleting the data writing operation corresponding to the file offset in the log file of the first machine room according to a preset deleting command containing the file offset.
In an alternative embodiment, the executable instructions further cause the processor to: and calling a first write thread according to the data write-in request after the packaging processing, and writing data corresponding to the data write-in operation into a Redis database of the first computer room.
In an alternative embodiment, the executable instructions further cause the processor to: and if the first machine room is down or in fault, switching the data service to the second machine room.
In an alternative embodiment, the log file format is an AOF format.
Fig. 3 is a schematic structural diagram of a computing device according to an embodiment of the present invention, and the specific embodiment of the present invention does not limit the specific implementation of the computing device.
As shown in fig. 3, the computing device may include: a processor (processor)302, a communication Interface 304, a memory 306, and a communication bus 308.
Wherein:
the processor 302, communication interface 304, and memory 306 communicate with each other via a communication bus 308.
A communication interface 304 for communicating with network elements of other devices, such as clients or other servers.
The processor 302 is configured to execute the program 310, and may specifically perform the relevant steps in the above-described data synchronization method embodiment.
In particular, program 310 may include program code comprising computer operating instructions.
The processor 302 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement an embodiment of the present invention. The computing device includes one or more processors, which may be the same type of processor, such as one or more CPUs; or may be different types of processors such as one or more CPUs and one or more ASICs.
And a memory 306 for storing a program 310. Memory 306 may comprise high-speed RAM memory and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
The program 310 may specifically be configured to cause the processor 302 to perform the following operations:
packaging a data write-in request sent by a client by using a preset write-in command;
calling a first write thread according to the data write-in request after encapsulation processing, and recording data write operation into a Redis cache region of a first machine room; calling a second write thread, writing data in the Redis cache region to a log file in a disk, and updating the file offset of the log file;
calling a reading thread to read data writing operation in the log file based on a preset reading command containing file offset, and synchronizing the read data writing operation to a second machine room by utilizing a synchronous link established between the machine rooms;
and writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room based on the preset synchronization command.
In an optional implementation manner, the preset synchronization command includes a machine room identifier and a file offset of the first machine room;
the program 310 also causes the processor 302 to perform the following operations: and recording the file offset corresponding to the synchronized data writing operation and the machine room identifier of the first machine room.
In an alternative embodiment, program 310 also causes processor 302 to: and if the synchronization link established between the machine rooms is broken to cause synchronization failure, executing the synchronization operation again from the breakpoint until the synchronization is successful.
In an alternative embodiment, program 310 further causes processor 302 to:
detecting whether the file offset recorded by the second machine room is consistent with the file offset carried by the preset synchronous command or not;
if the file offset carried by the preset synchronization command is smaller than the file offset recorded by the second machine room, discarding the synchronized data writing operation;
and if the file offset carried by the preset synchronization command is larger than the file offset recorded by the second computer room, writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room.
In an alternative embodiment, program 310 also causes processor 302 to: and deleting the data writing operation corresponding to the file offset in the log file of the first machine room according to a preset deleting command containing the file offset.
In an alternative embodiment, program 310 also causes processor 302 to: and calling a first write thread according to the data write-in request after the packaging processing, and writing data corresponding to the data write-in operation into a Redis database of the first computer room.
In an alternative embodiment, program 310 also causes processor 302 to: and if the first machine room is down or in fault, switching the data service to the second machine room.
In an alternative embodiment, the log file format is an AOF format.
The algorithms or displays presented herein are not inherently related to any particular computer, virtual system, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. In addition, embodiments of the present invention are not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the embodiments of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the invention and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the components according to embodiments of the present invention. The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names. The steps in the above embodiments should not be construed as limiting the order of execution unless specified otherwise.
The invention discloses: A1. a method of data synchronization, comprising:
packaging a data write-in request sent by a client by using a preset write-in command;
calling a first write thread according to the data write-in request after encapsulation processing, and recording data write operation into a Redis cache region of a first machine room; calling a second write thread, writing data in the Redis cache region to a log file in a disk, and updating the file offset of the log file;
calling a reading thread to read data writing operation in the log file based on a preset reading command containing file offset, and synchronizing the read data writing operation to a second machine room by utilizing a synchronous link established between the machine rooms;
and writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room based on the preset synchronization command.
A2. The method according to a1, wherein the preset synchronization command includes a machine room identifier and a file offset of a first machine room;
after writing the data corresponding to the synchronized data writing operation into the Redis database of the second computer room, the method further includes: and recording the file offset corresponding to the synchronized data writing operation and the machine room identifier of the first machine room.
A3. The method of a2, wherein the method further comprises: and if the synchronization link established between the machine rooms is broken to cause synchronization failure, executing the synchronization operation again from the breakpoint until the synchronization is successful.
A4. The method according to a3, wherein the writing data corresponding to the synchronized data writing operation to the Redis database of the second computer room based on the preset synchronization command further includes:
detecting whether the file offset recorded by the second machine room is consistent with the file offset carried by the preset synchronous command or not;
if the file offset carried by the preset synchronization command is smaller than the file offset recorded by the second machine room, discarding the synchronized data writing operation;
and if the file offset carried by the preset synchronization command is larger than the file offset recorded by the second computer room, writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room.
A5. The method of any one of a1-a4, wherein the method further comprises: and deleting the data writing operation corresponding to the file offset in the log file of the first machine room according to a preset deleting command containing the file offset.
A6. The method according to any of a1-a5, wherein after encapsulating a data write request sent by a client with a preset write command, the method further comprises: and calling a first write thread according to the data write-in request after the packaging processing, and writing data corresponding to the data write-in operation into a Redis database of the first computer room.
A7. The method according to any one of A1-A6, wherein after writing data corresponding to the synchronized data write operation to a Redis database of a second room based on a preset synchronization command, the method further comprises: and if the first machine room is down or in fault, switching the data service to the second machine room.
A8. The method of any of A1-A7, wherein the log file format is an AOF format.
B9. A computing device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is configured to store at least one executable instruction that causes the processor to:
packaging a data write-in request sent by a client by using a preset write-in command;
calling a first write thread according to the data write-in request after encapsulation processing, and recording data write operation into a Redis cache region of a first machine room; calling a second write thread, writing data in the Redis cache region to a log file in a disk, and updating the file offset of the log file;
calling a reading thread to read data writing operation in the log file based on a preset reading command containing file offset, and synchronizing the read data writing operation to a second machine room by utilizing a synchronous link established between the machine rooms;
and writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room based on the preset synchronization command.
B10. The computing device according to B9, wherein the preset synchronization command includes a machine room identifier and a file offset of the first machine room;
the executable instructions further cause the processor to: and recording the file offset corresponding to the synchronized data writing operation and the machine room identifier of the first machine room.
B11. The computing device of B10, wherein the executable instructions further cause the processor to: and if the synchronization link established between the machine rooms is broken to cause synchronization failure, executing the synchronization operation again from the breakpoint until the synchronization is successful.
B12. The computing device of B11, wherein the executable instructions further cause the processor to:
detecting whether the file offset recorded by the second machine room is consistent with the file offset carried by the preset synchronous command or not;
if the file offset carried by the preset synchronization command is smaller than the file offset recorded by the second machine room, discarding the synchronized data writing operation;
and if the file offset carried by the preset synchronization command is larger than the file offset recorded by the second computer room, writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room.
B13. The computing device of any one of B9-B12, wherein the executable instructions further cause the processor to: and deleting the data writing operation corresponding to the file offset in the log file of the first machine room according to a preset deleting command containing the file offset.
B14. The computing device of any one of B9-B13, wherein the executable instructions further cause the processor to: and calling a first write thread according to the data write-in request after the packaging processing, and writing data corresponding to the data write-in operation into a Redis database of the first computer room.
B15. The computing device of any one of B9-B14, wherein the executable instructions further cause the processor to: and if the first machine room is down or in fault, switching the data service to the second machine room.
B16. The computing device of any of B9-B15, wherein the log file format is an AOF format.
C17. A computer storage medium having at least one executable instruction stored therein, the executable instruction causing a processor to:
packaging a data write-in request sent by a client by using a preset write-in command;
calling a first write thread according to the data write-in request after encapsulation processing, and recording data write operation into a Redis cache region of a first machine room; calling a second write thread, writing data in the Redis cache region to a log file in a disk, and updating the file offset of the log file;
calling a reading thread to read data writing operation in the log file based on a preset reading command containing file offset, and synchronizing the read data writing operation to a second machine room by utilizing a synchronous link established between the machine rooms;
and writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room based on the preset synchronization command.
C18. The computer storage medium of C17, wherein the preset synchronization command includes a machine room identifier and a file offset of the first machine room;
the executable instructions further cause the processor to: and recording the file offset corresponding to the synchronized data writing operation and the machine room identifier of the first machine room.
C19. The computer storage medium of C18, wherein the executable instructions further cause the processor to: and if the synchronization link established between the machine rooms is broken to cause synchronization failure, executing the synchronization operation again from the breakpoint until the synchronization is successful.
C20. The computer storage medium of C19, wherein the executable instructions further cause the processor to:
detecting whether the file offset recorded by the second machine room is consistent with the file offset carried by the preset synchronous command or not;
if the file offset carried by the preset synchronization command is smaller than the file offset recorded by the second machine room, discarding the synchronized data writing operation;
and if the file offset carried by the preset synchronization command is larger than the file offset recorded by the second computer room, writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room.
C21. The computer storage medium of any one of C17-C20, wherein the executable instructions further cause the processor to: and deleting the data writing operation corresponding to the file offset in the log file of the first machine room according to a preset deleting command containing the file offset.
C22. The computer storage medium of any one of C17-C21, wherein the executable instructions further cause the processor to: and calling a first write thread according to the data write-in request after the packaging processing, and writing data corresponding to the data write-in operation into a Redis database of the first computer room.
C23. The computer storage medium of any one of C17-C22, wherein the executable instructions further cause the processor to: and if the first machine room is down or in fault, switching the data service to the second machine room.
C24. The computer storage medium of any of C17-C23, wherein the log file format is an AOF format.
Claims (10)
1. A method of data synchronization, comprising:
packaging a data write-in request sent by a client by using a preset write-in command;
calling a first write thread according to the data write-in request after encapsulation processing, and recording data write operation into a Redis cache region of a first machine room; calling a second write thread, writing data in the Redis cache region to a log file in a disk, and updating the file offset of the log file;
calling a reading thread to read data writing operation in the log file based on a preset reading command containing file offset, and synchronizing the read data writing operation to a second machine room by utilizing a synchronous link established between the machine rooms;
and writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room based on the preset synchronization command.
2. The method of claim 1, wherein the preset synchronization command comprises a machine room identifier and a file offset of a first machine room;
after writing the data corresponding to the synchronized data writing operation into the Redis database of the second computer room, the method further includes: and recording the file offset corresponding to the synchronized data writing operation and the machine room identifier of the first machine room.
3. The method of claim 2, wherein the method further comprises: and if the synchronization link established between the machine rooms is broken to cause synchronization failure, executing the synchronization operation again from the breakpoint until the synchronization is successful.
4. The method of claim 3, wherein the writing the data corresponding to the synchronized data writing operation to the Redis database of the second computer room based on the preset synchronization command further comprises:
detecting whether the file offset recorded by the second machine room is consistent with the file offset carried by the preset synchronous command or not;
if the file offset carried by the preset synchronization command is smaller than the file offset recorded by the second machine room, discarding the synchronized data writing operation;
and if the file offset carried by the preset synchronization command is larger than the file offset recorded by the second computer room, writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room.
5. The method according to any one of claims 1-4, wherein the method further comprises: and deleting the data writing operation corresponding to the file offset in the log file of the first machine room according to a preset deleting command containing the file offset.
6. The method according to any one of claims 1-5, wherein after encapsulating the data write request sent by the client with a preset write command, the method further comprises: and calling a first write thread according to the data write-in request after the packaging processing, and writing data corresponding to the data write-in operation into a Redis database of the first computer room.
7. The method according to any of claims 1-6, wherein after writing data corresponding to the synchronized data write operation to a Redis database of a second room based on a preset synchronization command, the method further comprises: and if the first machine room is down or in fault, switching the data service to the second machine room.
8. The method of any of claims 1-7, wherein the log file format is an AOF format.
9. A computing device, comprising: the system comprises a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface complete mutual communication through the communication bus;
the memory is configured to store at least one executable instruction that causes the processor to:
packaging a data write-in request sent by a client by using a preset write-in command;
calling a first write thread according to the data write-in request after encapsulation processing, and recording data write operation into a Redis cache region of a first machine room; calling a second write thread, writing data in the Redis cache region to a log file in a disk, and updating the file offset of the log file;
calling a reading thread to read data writing operation in the log file based on a preset reading command containing file offset, and synchronizing the read data writing operation to a second machine room by utilizing a synchronous link established between the machine rooms;
and writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room based on the preset synchronization command.
10. A computer storage medium having at least one executable instruction stored therein, the executable instruction causing a processor to:
packaging a data write-in request sent by a client by using a preset write-in command;
calling a first write thread according to the data write-in request after encapsulation processing, and recording data write operation into a Redis cache region of a first machine room; calling a second write thread, writing data in the Redis cache region to a log file in a disk, and updating the file offset of the log file;
calling a reading thread to read data writing operation in the log file based on a preset reading command containing file offset, and synchronizing the read data writing operation to a second machine room by utilizing a synchronous link established between the machine rooms;
and writing the data corresponding to the synchronized data writing operation into a Redis database of the second computer room based on the preset synchronization command.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910927251.7A CN110647511A (en) | 2019-09-27 | 2019-09-27 | Data synchronization method, computing device and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910927251.7A CN110647511A (en) | 2019-09-27 | 2019-09-27 | Data synchronization method, computing device and computer storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110647511A true CN110647511A (en) | 2020-01-03 |
Family
ID=68992990
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910927251.7A Pending CN110647511A (en) | 2019-09-27 | 2019-09-27 | Data synchronization method, computing device and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110647511A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111858501A (en) * | 2020-06-02 | 2020-10-30 | 武汉达梦数据库有限公司 | Log reading method and data synchronization system based on log analysis synchronization |
| CN111930781A (en) * | 2020-07-24 | 2020-11-13 | 北京金山云网络技术有限公司 | Method and device for processing data request of cache database |
| CN112000623A (en) * | 2020-08-07 | 2020-11-27 | 北京浪潮数据技术有限公司 | Metadata access method and device and computer readable storage medium |
| CN112052230A (en) * | 2020-09-02 | 2020-12-08 | 掌阅科技股份有限公司 | Multi-machine room data synchronization method, computing equipment and storage medium |
| CN112380292A (en) * | 2020-12-07 | 2021-02-19 | 厦门熵基科技有限公司 | Biological template data synchronization method, device, equipment and storage medium |
| CN112417043A (en) * | 2020-11-19 | 2021-02-26 | 百果园技术(新加坡)有限公司 | Data processing system and method |
| CN112925848A (en) * | 2021-02-23 | 2021-06-08 | 马上消费金融股份有限公司 | Data synchronization method, device, equipment and readable storage medium |
| CN114327289A (en) * | 2021-12-31 | 2022-04-12 | 展讯通信(天津)有限公司 | Data synchronization method and device and electronic equipment |
| WO2024055679A1 (en) * | 2022-09-14 | 2024-03-21 | 华为技术有限公司 | Data storage method, apparatus and system, and chip and acceleration device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105159795A (en) * | 2015-08-21 | 2015-12-16 | 小米科技有限责任公司 | Data synchronization method, apparatus and system |
| CN108804523A (en) * | 2018-04-27 | 2018-11-13 | 腾讯科技（深圳）有限公司 | Method of data synchronization, system and computer readable storage medium |
| CN109376197A (en) * | 2018-09-28 | 2019-02-22 | 掌阅科技股份有限公司 | A kind of method of data synchronization, server and computer storage medium |
| US20190245919A1 (en) * | 2018-02-05 | 2019-08-08 | Beijing Elex Technology Co., Ltd. | Method and apparatus for information processing, server and computer readable medium |
-
2019
- 2019-09-27 CN CN201910927251.7A patent/CN110647511A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105159795A (en) * | 2015-08-21 | 2015-12-16 | 小米科技有限责任公司 | Data synchronization method, apparatus and system |
| US20190245919A1 (en) * | 2018-02-05 | 2019-08-08 | Beijing Elex Technology Co., Ltd. | Method and apparatus for information processing, server and computer readable medium |
| CN108804523A (en) * | 2018-04-27 | 2018-11-13 | 腾讯科技（深圳）有限公司 | Method of data synchronization, system and computer readable storage medium |
| CN109376197A (en) * | 2018-09-28 | 2019-02-22 | 掌阅科技股份有限公司 | A kind of method of data synchronization, server and computer storage medium |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111858501A (en) * | 2020-06-02 | 2020-10-30 | 武汉达梦数据库有限公司 | Log reading method and data synchronization system based on log analysis synchronization |
| CN111858501B (en) * | 2020-06-02 | 2023-03-28 | 武汉达梦数据库股份有限公司 | Log reading method based on log analysis synchronization and data synchronization system |
| CN111930781A (en) * | 2020-07-24 | 2020-11-13 | 北京金山云网络技术有限公司 | Method and device for processing data request of cache database |
| CN112000623A (en) * | 2020-08-07 | 2020-11-27 | 北京浪潮数据技术有限公司 | Metadata access method and device and computer readable storage medium |
| CN112052230A (en) * | 2020-09-02 | 2020-12-08 | 掌阅科技股份有限公司 | Multi-machine room data synchronization method, computing equipment and storage medium |
| CN112052230B (en) * | 2020-09-02 | 2024-03-15 | 掌阅科技股份有限公司 | Multi-machine room data synchronization method, computing device and storage medium |
| CN112417043A (en) * | 2020-11-19 | 2021-02-26 | 百果园技术(新加坡)有限公司 | Data processing system and method |
| CN112380292B (en) * | 2020-12-07 | 2023-11-17 | 厦门熵基科技有限公司 | Biological template data synchronization method, device, equipment and storage medium |
| CN112380292A (en) * | 2020-12-07 | 2021-02-19 | 厦门熵基科技有限公司 | Biological template data synchronization method, device, equipment and storage medium |
| CN112925848A (en) * | 2021-02-23 | 2021-06-08 | 马上消费金融股份有限公司 | Data synchronization method, device, equipment and readable storage medium |
| CN112925848B (en) * | 2021-02-23 | 2024-02-06 | 马上消费金融股份有限公司 | Data synchronization method, device, equipment and readable storage medium |
| CN114327289B (en) * | 2021-12-31 | 2023-08-11 | 展讯通信(天津)有限公司 | Data synchronization method and device and electronic equipment |
| CN114327289A (en) * | 2021-12-31 | 2022-04-12 | 展讯通信(天津)有限公司 | Data synchronization method and device and electronic equipment |
| WO2024055679A1 (en) * | 2022-09-14 | 2024-03-21 | 华为技术有限公司 | Data storage method, apparatus and system, and chip and acceleration device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110647511A (en) | Data synchronization method, computing device and computer storage medium | |
| CN108234641B (en) | Data reading and writing method and device based on distributed consistency protocol | |
| US11403152B2 (en) | Task orchestration method and system | |
| CN110673941B (en) | Migration method of micro-services in multiple computer rooms, electronic equipment and storage medium | |
| US10545913B1 (en) | Data storage system with on-demand recovery of file import metadata during file system migration | |
| CN108228102B (en) | Method and device for data migration between nodes, computing equipment and computer storage medium | |
| CN111708738B (en) | Method and system for realizing interaction of hadoop file system hdfs and object storage s3 data | |
| CN106648832B (en) | Device and method for improving resource utilization rate of virtual machine | |
| WO2017113694A1 (en) | File synchronizing method, device and system | |
| CN112988281B (en) | Application starting method and device | |
| CN112052230B (en) | Multi-machine room data synchronization method, computing device and storage medium | |
| CN109582686B (en) | Method, device, system and application for ensuring consistency of distributed metadata management | |
| CN111615692A (en) | Data transfer method, calculation processing device, and storage medium | |
| CN112015595B (en) | Master-slave database switching method, computing device and storage medium | |
| CN111880956A (en) | Data synchronization method and device | |
| CN108228812B (en) | Self-adaptive main node switching method and device | |
| CN113794764A (en) | Request processing method and medium for server cluster and electronic device | |
| US10387274B2 (en) | Tail of logs in persistent main memory | |
| CN105302489A (en) | Heterogeneous multi-core remote embedded memory system and method | |
| CN115686932A (en) | Backup set file recovery method and device and computer equipment | |
| WO2020233001A1 (en) | Distributed storage system comprising dual-control architecture, data reading method and device, and storage medium | |
| US10740159B2 (en) | Synchronization object prioritization systems and methods | |
| CN112035418A (en) | Multi-computer room synchronization method, computing device and computer storage medium | |
| CN111090782A (en) | Graph data storage method, device, equipment and storage medium | |
| CN108062224B (en) | Data reading and writing method and device based on file handle and computing equipment |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200103 |