CN116756108A - A file synchronization method, system, device and readable storage medium - Google Patents

Abstract

This application discloses a file synchronization method, system, device and readable storage medium, which can be used in the distributed field or financial field. The first server sends the file model information of the first server to each second server; the file model information of the first server includes the first file identification, and the first file identification includes the file identification of the local file of the first server. Therefore, the second server The server receives the file model information of the first server, verifies whether the files indicated by each first file identifier have been synchronized, obtains the synchronization verification result, and sends the synchronization verification result to the first server. The first server receives the synchronization verification result sent by the second server. After synchronizing the verification results, the unsynchronized files in the synchronization verification results are sent to the second server. Since the first server and the second server are any two servers in the distributed system, it can be seen that this solution realizes file synchronization of multiple servers in the distributed system in parallel and improves the file synchronization efficiency.

Description

A file synchronization method, system, device and readable storage medium

Technical field

The present application relates to the field of distributed technology, and in particular, to a file synchronization method, system, device and readable storage medium.

Background technique

Deployment of distributed services is a key project of the banking system, and file synchronization in distributed services is the top priority of project deployment. At present, there is a common phenomenon of untimely file synchronization in the operation of distributed services. Untimely file synchronization often causes problems. An abnormal situation that causes one server to upload a file and another (one or more) servers to be unable to download the file. This is a serious system defect and may even cause the project to run abnormally. Therefore, how to efficiently implement a distributed system File synchronization is a technical problem that needs to be solved urgently.

Contents of the invention

This application provides a file synchronization method, system, device and readable storage medium, with the purpose of improving the efficiency of file synchronization in distributed systems, as follows:

A file synchronization method, applied to a distributed system, the distributed system includes multiple servers constructed in a distributed manner, the method includes:

The first server obtains the file model information of the first server and sends the file model information of the first server to each second server; wherein the file model information of the first server includes a first file identifier, so The first file identification includes the file identification of the local file of the first server, the first server includes any one of the multiple servers, and the second server includes the multiple servers except the Any server other than the first server;

The second server receives the file model information of the first server, verifies whether each file indicated by the first file identifier has been synchronized, and obtains a synchronization verification result. The synchronization verification result includes files of unsynchronized files. logo;

The second server sends the synchronization verification result to the first server;

After receiving the synchronization verification result sent by the second server, the first server sends the unsynchronized files in the synchronization verification result to the second server.

Optionally, the first server obtains the file model information of the first server, including:

The first server acquires the file model information of the first server in response to reaching a preset synchronization opportunity;

Wherein, reaching the preset synchronization timing includes: reaching the synchronization time of the preset synchronization cycle, and/or detecting an update of the local file, and the update includes deletion and/or addition.

Optionally, the first server obtains the file model information of the first server, including:

The first server obtains the file name of each first file, and the first file includes a local file of the first server;

The first server uses a preset information digest algorithm to generate a hash value of the file name of each first file as a file identifier of each first file to obtain the file model information of the first server.

Optionally, the second server receives the file model information of the first server, verifies whether each file indicated by the first file identifier has been synchronized, and obtains a synchronization verification result, including:

The second server obtains the file model information of the second server, the file model information of the second server includes a second file identifier, and the second file identifier includes a file identifier of a local file of the second server;

The second server obtains a file identifier that satisfies the first preset condition as the file identifier of the unsynchronized file based on the file model information of the second server and the file model information of the first server. The preset conditions include: existing in the file model information of the first server and not existing in the file model information of the second server;

The second server generates the synchronization verification result, and the synchronization verification result includes the file identification of each of the unsynchronized files.

Optionally, the file model information of the target server also includes synchronization status information of each file identification. The synchronization status information includes a server identification and a corresponding synchronization status identification. The synchronization status identification corresponding to the server identification is used to indicate that the server Whether the server indicated by the identification has synchronized the file indicated by the file identification, and the target server includes a first server and a second server;

After the second server obtains the file model information of the second server, the method further includes:

Based on the file model information of the second server and the file model information of the first server, the second server obtains a file identifier that satisfies a second preset condition as the file identifier of the differential synchronization file. The second preset The conditions include: existing in the file model information of the second server, and in the file model information of the first server, the synchronization status identifier corresponding to the server identifier of the second server is unsynchronized;

The synchronization verification result also includes the file identification of each differential synchronization file.

Optionally, the first server sends the unsynchronized files in the synchronization verification result to the second server, including:

If the synchronization verification result includes the file identifier of the unsynchronized file, the first server sends the unsynchronized file to the second server, and adds the file identifier of the unsynchronized file to the synchronization status information. , the synchronization status identifier corresponding to the identifier of the second server is updated to synchronized;

The method also includes:

If the synchronization verification result includes the file identification of the differential synchronization file, the first server updates the synchronization status identification corresponding to the identification of the second server in the synchronization status information of the file identification of the differential synchronization file. is synchronized.

Optionally, each server among the multiple servers pre-constructs a first sending queue, a second sending queue, a first receiving queue, a second receiving queue and a file upload queue;

The first server sends the file model information of the first server to each second server, including:

The first server sends the file model information of the first server to each of the second servers through the first sending queue;

The second server receives the file model information of the first server, including:

The second server receives the file model information of the first server through the first receiving queue;

The second server sends the synchronization verification result to the first server, including:

The second server sends the synchronization verification result to the first server through the second sending queue;

The first server receives the synchronization verification result sent by the second server, including:

The first server receives the synchronization verification results sent by each of the second servers through the second receiving queue;

The first server sends the unsynchronized files in the synchronization verification result to the second server, including:

The first server sends the unsynchronized files in the synchronization verification result to the second server through the file upload queue.

A file synchronization system, including multiple servers built in a distributed manner; among them, the target server is used for:

Obtain the file model information of the target server; wherein the file model information of the target server includes a target file identification, the target file identification includes a file identification of a local file of the target server, and the target server includes the multiple any server among the servers;

Send the file model information of the target server to each other server, so that the other servers receive the file model information of the target server, verify whether the files indicated by each target file identifier have been synchronized, and obtain synchronization verification As a result, the synchronization verification result is sent to the target server; wherein the other servers include any server among the multiple servers except the target server, and the synchronization verification result includes the unsynchronized file. File identification;

After receiving the synchronization verification result sent by the other server, the unsynchronized files in the synchronization verification result are sent to the other server.

A file synchronization device applied to a target server in a distributed system. The distributed system includes multiple servers constructed in a distributed manner. The target server includes any server among the multiple servers; the device includes :

A file information acquisition unit configured to acquire file model information of the target server; wherein the file model information of the target server includes a target file identifier, and the target file identifier includes a file identifier of a local file of the target server;

The file information sending unit is used to send the file model information of the target server to each other server, so that the other servers receive the file model information of the target server and verify whether each target file identification indication has been synchronized. files, generate and send synchronization verification results to the target server; wherein the other servers include any server among the multiple servers except the target server, and the synchronization verification results include unsynchronized files file identification;

The file uploading unit is configured to send the unsynchronized files in the synchronization verification results to the other servers after receiving the synchronization verification results sent by the other servers.

A readable storage medium on which a computer program is stored. When the computer program is executed by a processor, each step of the file synchronization method is implemented.

It can be seen from the above technical solutions that in the file synchronization method, system, device and readable storage medium provided by the embodiments of the present application, the file model information sent by the first server to each second server includes the file identification of the local file of the first server. , each second server verifies whether each local file of the first server has been synchronized in the local file according to the file identification of the local file of the second server, and if there is an unsynchronized file, feeds back the file identification of the unsynchronized file to The first server can send corresponding unsynchronized files to each second server based on the file identifier of the unsynchronized file fed back by each second server. The first server includes any server among multiple servers constructed in a distributed manner. , the second server includes any server among multiple servers except the first server. It can be seen that this application realizes parallel synchronization of local files in the first server to various other servers, improving the efficiency of file synchronization.

Description of the drawings

In order to explain the embodiments of the present application or the technical solutions in the prior art more clearly, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are only These are some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without exerting creative efforts.

Figure 1 is a schematic structural diagram of a file synchronization system provided by an embodiment of the present application;

Figure 2 is a schematic flowchart of a specific implementation of a file synchronization method provided by an embodiment of the present application;

Figure 3 is a schematic flow chart of a file synchronization method provided by an embodiment of the present application;

Figure 4 is a schematic structural diagram of a file synchronization device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this application.

The file synchronization method provided by the embodiment of the present application can be applied to the file synchronization system. As shown in Figure 1, the file synchronization system provided by the embodiment of the present application includes multiple servers constructed in a distributed manner, namely server 1 to server n. Each server Each has its own local file stored. Any server in this system, that is, the target server, is used for:

Obtain the file model information of the target server, send the file model information of the target server to each other server, so that the other servers receive the file model information of the target server, verify whether the files indicated by each target file identifier have been synchronized, and generate and send synchronization Verify the results to the target server. After receiving the synchronization verification results sent by other servers, send the unsynchronized files in the synchronization verification results to other servers. The file model information of the target server includes the target file identifier, the target file identifier includes the file identifier of the local file of the target server, and the synchronization verification result includes the file identifier of the unsynchronized file.

It can be seen that the file model information sent by any target server to each other server in this system includes the file identification of the local file of the target server. Therefore, each other server can verify the file identification of other servers based on the file identification of the local file of the target server. Whether each local file of the target server has been synchronized in the local file, and if there are unsynchronized files, the file ID of the unsynchronized file is fed back to the target server. Further, the target server can further use the file ID of the unsynchronized file fed back by other servers. , sending corresponding unsynchronized files to each other server, thereby realizing file synchronization of each server in the distributed system. Since the target server is any server in the distributed system, it can be seen that the file synchronization method provided by this method can realize each server in parallel. Server file synchronization, thus improving the efficiency of file synchronization.

Taking a distributed system including a first server and multiple second servers as an example, Figure 2 is a flow chart of a specific implementation method of the file synchronization method provided by the embodiment of the present application. As shown in Figure 2, this method includes:

S201. The first server acquires the file model information of the first server in response to the synchronization time reaching the preset synchronization cycle.

In this embodiment, the synchronization period can be pre-configured. For example, the synchronization period is 24 hours, and the synchronization time of the synchronization period is 10 a.m., that is, the first server obtains the file model information of the first server at 10 a.m. every day. , start the file synchronization process.

In this embodiment, the file model information of the target server (including the first server and each second server) in the distributed system includes the target file identification and the synchronization status information of each target file identification, where the synchronization status information includes the server identification and The corresponding synchronization status identifier. The synchronization status identifier corresponding to the server identifier is used to indicate whether the server referred to by the server identifier has synchronized the file referred to by the file identifier. Optionally, the server identifier includes the server IP address.

For example, the file model information of the first server includes the first file identifier and the synchronization status information of each first file identifier, where the first file identifier includes the file identifier of the local file of the first server, and the synchronization status information of any first file identifier. The status information includes the server identification of each second server and the corresponding synchronization status identification. The synchronization status identification includes unsynchronized and synchronized. If in the synchronization status information of the first file identification A1, the server identification corresponding to the second server S2 If the synchronization status is marked as unsynchronized, it indicates that S2 has not synchronized with A1.

In this embodiment, the method for the first server to obtain the file model information of the first server specifically includes:

First, the first server obtains the file name of each first file.

Wherein, the first file includes a local file of the first server, and the specific method of obtaining the file name of the local file can be found in the prior art.

Then, the first server uses a preset information digest algorithm to generate a hash value of the file name of each first file as a file identification of each first file.

In this embodiment, the message digest algorithm includes MD5 (Message Digest Algorithm MD5, message digest algorithm version 5).

Finally, the first server obtains the server identification of each second server and the synchronization status identification corresponding to each second server identification through historical information.

It should be noted that the historical information includes the file model information stored by the first server after the file synchronization process triggered by the previous synchronization cycle ends. If there is no synchronization status identification corresponding to the server identification of the second server, the default synchronization status identification is unsynchronized.

It is understandable that the hash value of the file name generated by the MD5 algorithm is 16 bytes in size, which takes up less storage space than the file name, improves information transmission efficiency, and can send more file information in a single network request. The corresponding relationship between the server IP address and the synchronization status identifier can make it easy to verify whether each file is completely synchronized to each server, and also facilitate the location of the server corresponding to the unsynchronized file.

S202. The first server sends the file model information of the first server to each second server. S203. After receiving the file model information of the first server, the second server obtains the file model information of the second server.

In this embodiment, the file model information of the second server includes the second file identifier and the synchronization status information of each second file identifier.

S204. Based on the file model information of the second server and the file model information of the first server, the second server obtains the file identifier that satisfies the first preset condition as the file identifier of the unsynchronized file.

In this embodiment, the first preset condition includes: it exists in the file model information of the first server and does not exist in the file model information of the second server.

It can be understood that the file indicated by the file identification that meets the first preset condition is a local file that exists on the first server, but does not exist in the local file of the second server, that is, it is not synchronized to the second server. document.

S205. Based on the file model information of the second server and the file model information of the first server, the second server obtains the file identifier that satisfies the second preset condition as the file identifier of the differential synchronization file.

In this embodiment, the second preset condition includes: it exists in the file model information of the second server, and in the file model information of the first server, the synchronization status identifier corresponding to the server identifier of the second server is unsynchronized.

It can be understood that the file indicated by the file identification that meets the second preset condition exists in the local files of the first server and the second server at the same time. However, in the file model information of the first server, the server identification of the second server The corresponding synchronization status indicator is still unsynchronized, that is, in the file model information of the first server, the second server has not synchronized the file by default. Obviously, the file model information of the first server is wrong and needs to be updated.

S206. The second server generates a synchronization verification result and sends the synchronization verification result to the first server.

In this embodiment, the synchronization verification result includes the file identification of each unsynchronized file and the file identification of each differential synchronization file.

S207. The first server receives the synchronization verification results sent by each second server, and determines whether the synchronization verification results include the file identification of the unsynchronized file or the file identification of the differential synchronization file. In this embodiment, different types of file identifiers are recorded between servers according to preconfigured type identification rules. For example, the file identifier of an unsynchronized file carries a preset unsynchronized identifier, and the file identifier of a differentially synchronized file carries a preset difference identifier. , determine whether there is a file ID of an unsynchronized file or a file ID of a differentially synchronized file by looking for the type ID.

Further, if there is a file identifier of an unsynchronized file, execute S208. If there is a file identifier of a differentially synchronized file, execute S209. It should be noted that the synchronization verification result may contain both the file identifier of the unsynchronized file and the identifier of the differentially synchronized file. file identification, then S208 and S209 can be executed in parallel or serially according to preset execution rules, which is not limited in this embodiment.

S208. After sending the unsynchronized file in the synchronization verification result to the second server, the first server updates the synchronization status identifier corresponding to the identifier of the second server in the synchronization status information of the file identifier of the unsynchronized file to synchronized.

It should be noted that after the first server sends the unsynchronized file in the synchronization verification result to the second server, it can directly update the synchronization status identifier corresponding to the identifier of the second server in the synchronization status information of the file identifier of the unsynchronized file. If the file has been synchronized, you can also wait for the second server to complete the synchronization of the unsynchronized file and feedback the synchronization completion notification, and then update the synchronization status identifier corresponding to the second server's identifier in the synchronization status information of the file identifier of the unsynchronized file to "synchronized". Synchronization, this embodiment does not limit this.

S209. The first server updates the synchronization status identification corresponding to the identification of the second server in the synchronization status information of the file identification of the differential synchronization file to synchronized.

It can be seen from the above technical solution that in the file synchronization method provided by the embodiment of the present application, the file model information sent by the first server to each second server includes the file identification of the local file of the first server. The file identifier of the local file of the second server verifies whether each local file of the first server has been synchronized in the local file, and if there are unsynchronized files, feeds back the file identifier of the unsynchronized file to the first server. The first server According to the file identification of the unsynchronized files fed back by each second server, the corresponding unsynchronized files can be sent to each second server, thereby achieving parallel synchronization of local files in the first server to each other server, improving the efficiency of file synchronization. efficiency.

Furthermore, the file model information also includes synchronization status information of each file identifier. On the one hand, the first server can locate the server corresponding to the unsynchronized file through the synchronization status information of each file identifier, and send the corresponding unsynchronized file to the server. On the one hand, the second server can obtain unsynchronized files and differential synchronization files by receiving file model information verification, thereby achieving file synchronization while achieving consistency in file synchronization status between servers.

Furthermore, the file synchronization method provided by this application is zero-invasive when applied to each server, does not involve modifying the original code of the task, and abandons the shortcomings of system bloat and information redundancy caused by traditional third-party frameworks to achieve file synchronization.

It should be noted that the file synchronization method shown in Figure 2 is only an optional specific implementation method. The file synchronization method provided by this application can also be executed through other optional implementation methods:

For example, the synchronization time to reach the synchronization cycle is only an optional synchronization opportunity. In an optional implementation, after the first server detects that the local file is updated, the first server obtains the file model information, where, Updates include deletions and/or additions. That is, by monitoring the local file directory, the updated file names are obtained in real time, and the file model information is obtained.

For another example, when the synchronization time is reached, the specific method of obtaining the file model information may be to obtain the stored historical file model information. After detecting that the local file is updated, the specific method of obtaining the file model information may be to obtain the stored historical file model information. File model information, and updates historical file model information based on file update status.

For another example, in an optional implementation, each server pre-constructs a first sending queue for sending file model information, a second sending queue for feeding back synchronization verification results, and a second sending queue for receiving file model information. A first receiving queue for information, a second receiving queue for receiving synchronization verification results, and a file upload queue for sending unsynchronized files.

Specifically, the first server sends the file model information of the first server to each second server through the first sending queue. The second server receives the file model information of the first server through the first receiving queue. The second server sends the synchronization verification result to the first server through the second sending queue. The first server receives the synchronization verification results sent by each second server through the second receiving queue. The first server sends the unsynchronized files in the synchronization verification result to the second server through the file upload queue.

It can be seen that each server realizes the orderly synchronization of sending and receiving file model information, sending and receiving synchronization verification results, and sending unsynchronized files through pre-built queues, effectively solving the problem of unstable system operation and problems when synchronizing a large number of files. The problem of slow information transfer.

For another example, in an optional embodiment, when the first server sends the file model information of the first server to each second server through the first sending queue, the first server can send the file model information of the first server to each second server through the preset sending rule. The batch data in the file model information is sent to the second server in batches. Specifically, the file model information of the first server includes N target file identifiers and synchronization status information of the target file identifier. Due to the large number of N, the first server The server may send n pieces of target file identification and synchronization status information of the target file identification to the second server at a preset time interval until all the file model information of the first server is sent to the second server.

For another example, in an optional embodiment, the first server persists the synchronization completion information. The synchronization completion information includes synchronized information in the file model information of the first server, and the synchronized information includes a file identifier, a server identifier, and a synchronized identifier. Based on this, in response to reaching the synchronization time of the preset synchronization cycle, the file model information of the first server obtained by the first server includes file model information that has not been persisted.

In summary, a file synchronization method provided by the embodiment of the present application is summarized as a process shown in Figure 3. As shown in Figure 3, this method specifically includes:

S301. The first server obtains the file model information of the first server, and sends the file model information of the first server to each second server.

Wherein, the file model information of the first server includes a first file identification, and the first file identification includes a file identification of a local file of the first server.

S302. The second server receives the file model information of the first server, verifies whether the files indicated by each first file identifier have been synchronized, and obtains the synchronization verification result.

Among them, the synchronization verification result includes the file identifier of the unsynchronized file.

S303. The second server sends the synchronization verification result to the first server.

S304. After receiving the synchronization verification result sent by the second server, the first server sends the unsynchronized file in the synchronization verification result to the second server.

It can be seen from the above technical solution that in the file synchronization method provided by the embodiment of the present application, the file model information sent by the first server to each second server includes the file identification of the local file of the first server. The file identifier of the local file of the second server verifies whether each local file of the first server has been synchronized in the local file, and if there are unsynchronized files, feeds back the file identifier of the unsynchronized file to the first server. The first server The corresponding unsynchronized file can be sent to each second server according to the file identification of the unsynchronized file fed back by each second server. The first server includes any one of multiple servers constructed in a distributed manner, and the second server includes multiple servers. For any server among the servers except the first server, it can be seen that this application synchronizes local files in the first server to various other servers in parallel, thereby improving the efficiency of file synchronization.

This application also provides a file synchronization device, which can be applied to any one of multiple distributed servers. Figure 4 shows a schematic structural diagram of the file synchronization device. The device includes:

The file information obtaining unit 401 is used to obtain the file model information of the target server; wherein the file model information of the target server includes a target file identification, and the target file identification includes a file identification of a local file of the target server;

The file information sending unit 402 is used to send the file model information of the target server to each other server, so that the other servers receive the file model information of the target server and verify whether each target file identifier has been synchronized. The indicated file generates and sends synchronization verification results to the target server; wherein, the other servers include any server among the multiple servers except the target server, and the synchronization verification results include unsynchronized The file identifier of the file;

The file upload unit 403 is configured to send the unsynchronized files in the synchronization verification result to the other server after receiving the synchronization verification result sent by the other server.

As an example, this application also provides application scenarios and specific implementation methods of a file synchronization method, as follows:

Currently, many projects have scenarios that require the deployment of distributed services, and file services are generally necessary. However, in distributed scenarios, file services have to consider file synchronization issues, because after uploading files, The abnormal situation that the file cannot be downloaded from another server is a serious system defect. The specific technical problems that need to be overcome are as follows:

1. Real-time file synchronization.

2. Integrating third-party frameworks will cause the project to become bloated and destroy the version management of the project code.

3. Reduce the intrusiveness of existing project code.

4. In a multi-server environment, file synchronization efficiency is low.

5. With a large number of files, the complexity of file synchronization increases.

Currently, commonly used file synchronization methods include integrating third-party frameworks to achieve distributed file storage. However, integrating third-party frameworks not only results in bloated project code, but also requires a large amount of changes to existing project codes, which in turn affects the version management of the project code.

In order to overcome the above technical problems, this application provides a structure of a file synchronization device specifically applied to each server, including:

File model is used to construct file model information. Through the construction of file model information, the definition of file parameter information is simplified. Specifically, the hash value is the value generated by the md5 algorithm for the file name. The size is 16 bytes. Generally speaking, it is relatively large. The file name occupies a small storage space, which improves file transmission efficiency to a certain extent. More file information can be sent with a single network request. The IP set and completion identifier are used to verify whether the file is completely synchronized to each server and are also used for synchronization. In the policy, send file model information to the specified server or upload files.

The file monitoring module is used to monitor whether file changes occur in the specified file directory. Through the monitoring module, real-time synchronization of files is achieved.

File receiving module, used to receive files.

File upload module, used to upload files.

Through the file queue, orderly parallel processing of file synchronization and reception is realized, effectively dealing with the problem of unstable and slow synchronization of a large number of files.

The file verification module is used to update the file model information corresponding to the server, verify the file synchronization completion status, and persist the success information locally. Through the verification module, it updates the file model information corresponding to the server and verifies the file synchronization completion status. , and persist the success information locally.

The file synchronization module is used to use file queues and synchronization strategies to achieve parallel synchronization processing of files. Through the file synchronization module and the many-to-many synchronization strategy, between multiple servers, each server sends local file model information in batches to other servers at the same time to obtain the comparison results, which are subsequently processed by the verification module and synchronization module to achieve file synchronization. . If multiple servers are synchronized in a serial order, the efficiency will be greatly reduced. Multiple servers work in parallel, reducing idle time and improving efficiency. The synchronization module will perform initial file synchronization after the program is started, and also has a scheduled synchronization strategy to ensure complete synchronization in the event of system abnormalities.

Among them, each module is independent of each other and connected one by one to ensure full and efficient synchronization of distributed system files. Existing projects are integrated as separate modules, with zero intrusion and no modification of the original code of the task.

To sum up, this solution has at least the following technical effects:

1. Implement file model definition and standardized definition: hash value, server IP and completion identification set, which is conducive to data batch transmission and optimizes code logic processing.

2. Implement file queues to achieve orderly sending and receiving of files. For scenarios with a large number of files, setting the queue threshold can also be well handled.

3. Implement the file synchronization strategy and adopt a many-to-many synchronization strategy, which requires simultaneous data interaction between multiple servers.

4. File verification, used to update the file model information corresponding to the server, verify the file synchronization completion status, and persist the successful information locally.

Embodiments of the present application also provide a readable storage medium that can store a computer program suitable for execution by a processor. When the computer program is executed by the processor, a file synchronization method provided by an embodiment of the present application is implemented. The various steps are as follows:

The first server obtains the file model information of the first server and sends the file model information of the first server to each second server; wherein the file model information of the first server includes a first file identifier, so The first file identification includes the file identification of the local file of the first server, the first server includes any one of the multiple servers, and the second server includes the multiple servers except the Any server other than the first server;

The second server receives the file model information of the first server, verifies whether each file indicated by the first file identifier has been synchronized, and obtains a synchronization verification result. The synchronization verification result includes files of unsynchronized files. logo;

The second server sends the synchronization verification result to the first server;

After receiving the synchronization verification result sent by the second server, the first server sends the unsynchronized files in the synchronization verification result to the second server.

It should be noted that the file synchronization method, system, device and readable storage medium provided by the present invention can be used in the distributed field or the financial field. The above are only examples and do not limit the application fields of the file synchronization method, system, device and readable storage medium provided by the present invention.

Finally, it should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that these entities or any such actual relationship or sequence between operations. Furthermore, the terms "comprises," "comprises," or any other variations thereof are intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus that includes a list of elements includes not only those elements, but also those not expressly listed other elements, or elements inherent to the process, method, article or equipment. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article, or apparatus that includes the stated element.

Each embodiment in this specification is described in a progressive manner. Each embodiment focuses on its differences from other embodiments. The same and similar parts between the various embodiments can be referred to each other.

The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be practiced in other embodiments without departing from the spirit or scope of the application. Therefore, the present application is not to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. A file synchronization method, characterized in that it is applied to a distributed system, the distributed system includes multiple servers constructed in a distributed manner, and the method includes: The first server obtains the file model information of the first server and sends the file model information of the first server to each second server; wherein the file model information of the first server includes a first file identifier, so The first file identification includes the file identification of the local file of the first server, the first server includes any one of the multiple servers, and the second server includes the multiple servers except the Any server other than the first server; The second server receives the file model information of the first server, verifies whether each file indicated by the first file identifier has been synchronized, and obtains a synchronization verification result. The synchronization verification result includes files of unsynchronized files. logo; The second server sends the synchronization verification result to the first server; After receiving the synchronization verification result sent by the second server, the first server sends the unsynchronized files in the synchronization verification result to the second server. 2. The method according to claim 1, wherein the first server obtains the file model information of the first server, including: The first server acquires the file model information of the first server in response to reaching a preset synchronization opportunity; Wherein, reaching the preset synchronization timing includes: reaching the synchronization time of the preset synchronization cycle, and/or detecting an update of the local file, and the update includes deletion and/or addition. 3. The method according to claim 1, wherein the first server obtains the file model information of the first server, including: The first server obtains the file name of each first file, and the first file includes a local file of the first server; The first server uses a preset information digest algorithm to generate a hash value of the file name of each first file as a file identifier of each first file to obtain the file model information of the first server. 4. The method according to claim 1, characterized in that the second server receives the file model information of the first server, verifies whether the files indicated by each of the first file identifiers have been synchronized, and obtains the synchronized calibration. Test results include: The second server obtains the file model information of the second server, the file model information of the second server includes a second file identifier, and the second file identifier includes a file identifier of a local file of the second server; The second server obtains a file identifier that satisfies the first preset condition as the file identifier of the unsynchronized file based on the file model information of the second server and the file model information of the first server. The preset conditions include: existing in the file model information of the first server and not existing in the file model information of the second server; The second server generates the synchronization verification result, and the synchronization verification result includes the file identification of each of the unsynchronized files. 5. The method according to claim 4, characterized in that the file model information of the target server also includes synchronization status information of each file identification, and the synchronization status information includes a server identification and a corresponding synchronization status identification, and the server identification The corresponding synchronization status identifier is used to indicate whether the server referred to by the server identifier has synchronized the file referred to by the file identifier, and the target server includes a first server and a second server; After the second server obtains the file model information of the second server, the method further includes: Based on the file model information of the second server and the file model information of the first server, the second server obtains a file identifier that satisfies a second preset condition as the file identifier of the differential synchronization file. The second preset The conditions include: existing in the file model information of the second server, and in the file model information of the first server, the synchronization status identifier corresponding to the server identifier of the second server is unsynchronized; The synchronization verification result also includes the file identification of each differential synchronization file. 6. The method of claim 5, wherein the first server sends the unsynchronized files in the synchronization verification result to the second server, including: If the synchronization verification result includes the file identifier of the unsynchronized file, the first server sends the unsynchronized file to the second server, and adds the file identifier of the unsynchronized file to the synchronization status information. , the synchronization status identifier corresponding to the identifier of the second server is updated to synchronized; The method also includes: If the synchronization verification result includes the file identification of the differential synchronization file, the first server updates the synchronization status identification corresponding to the identification of the second server in the synchronization status information of the file identification of the differential synchronization file. is synchronized. 7. The method according to claim 1, characterized in that each of the plurality of servers has a first sending queue, a second sending queue, a first receiving queue, a second receiving queue and a file upload in advance. queue; The first server sends the file model information of the first server to each second server, including: The first server sends the file model information of the first server to each of the second servers through the first sending queue; The second server receives the file model information of the first server, including: The second server receives the file model information of the first server through the first receiving queue; The second server sends the synchronization verification result to the first server, including: The second server sends the synchronization verification result to the first server through the second sending queue; The first server receives the synchronization verification result sent by the second server, including: The first server receives the synchronization verification results sent by each of the second servers through the second receiving queue; The first server sends the unsynchronized files in the synchronization verification result to the second server, including: The first server sends the unsynchronized files in the synchronization verification result to the second server through the file upload queue. 8. A file synchronization system, characterized by including multiple servers constructed in a distributed manner; wherein the target server is used for: Obtain the file model information of the target server; wherein the file model information of the target server includes a target file identification, the target file identification includes a file identification of a local file of the target server, and the target server includes the multiple any server among the servers; Send the file model information of the target server to each other server, so that the other servers receive the file model information of the target server, verify whether the files indicated by each target file identifier have been synchronized, and obtain synchronization verification As a result, the synchronization verification result is sent to the target server; wherein the other servers include any server among the multiple servers except the target server, and the synchronization verification result includes the unsynchronized file. File identification; After receiving the synchronization verification result sent by the other server, the unsynchronized files in the synchronization verification result are sent to the other server. 9. A file synchronization device, characterized in that it is applied to a target server in a distributed system, the distributed system includes multiple servers constructed in a distributed manner, and the target server includes any one of the multiple servers. Server; the device includes: A file information acquisition unit configured to acquire file model information of the target server; wherein the file model information of the target server includes a target file identifier, and the target file identifier includes a file identifier of a local file of the target server; The file information sending unit is used to send the file model information of the target server to each other server, so that the other servers receive the file model information of the target server and verify whether each target file identification indication has been synchronized. files, generate and send synchronization verification results to the target server; wherein the other servers include any server among the multiple servers except the target server, and the synchronization verification results include unsynchronized files file identification; The file uploading unit is configured to send the unsynchronized files in the synchronization verification results to the other servers after receiving the synchronization verification results sent by the other servers. 10. A readable storage medium with a computer program stored thereon, characterized in that when the computer program is executed by a processor, each step of the file synchronization method as claimed in any one of claims 1 to 7 is implemented. .