Distributed file uploading verification method and device, equipment and storage medium

By monitoring and verifying the upload status of each data block in a distributed file storage system in real time, the problem of data loss or corruption during file upload is solved, the data integrity and reliability are guaranteed, and storage and transmission are reduced cost.

CN119004546AActive Publication Date: 2024-11-22PING AN BANK CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
CN202411086428.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-08
Publication Date
2024-11-22
Estimated Expiration
2044-08-08

AI Technical Summary

Technical Problem

The existing distributed file storage system is susceptible to the network environment during file uploading, resulting in unstable data transmission speed, which may lead to data loss or damage. It lacks real-time monitoring and feedback mechanisms, so it is impossible to detect data during file uploading in a timely manner. Integrity issues lead to increased storage and transmission costs.

Method used

By splitting the file to be uploaded into multiple data blocks, the upload status of each data block is monitored in real time, and the Uploading link list and the Upload-Result link list are integrated and compared, and abnormal data blocks are detected and processed in a timely manner to ensure data integrity and Reliability and improve efficiency through multi-threaded uploads.

Benefits of technology

Real-time monitoring and verification of the file upload process is realized, ensuring data integrity and accuracy, reducing storage and transmission costs, and improving user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119004546A_ABST
    Figure CN119004546A_ABST
Patent Text Reader

Abstract

The invention relates to a distributed file uploading verification method, which comprises the following steps: acquiring a to-be-uploaded file, splitting the to-be-uploaded file into a plurality of data blocks according to a preset threshold value, and uploading the plurality of data blocks to a distributed file system; uploading information of each data block is obtained through the distributed file system, and the uploading information of each data block is stored in an Uploading chain table; the upload information in the Uploading chain table is integrated to obtain integrated data, the integrated data comprises the upload information of each data block, and the integrated data is uploaded to the Upload-Result chain table; the integrated data of the Upload-Result chain table is monitored in real time, and when it is monitored that data blocks which are successfully uploaded exist, the data blocks which are successfully uploaded are compared through a distributed file system; if the successfully uploaded data block is abnormal, prompting a user that the uploading is abnormal; if all the data blocks are not abnormal, the user is prompted to upload successfully. According to the method, the uploading state of each data block is monitored and verified in real time, so that the integrity and the accuracy of the data are ensured.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of distributed file storage systems, and in particular to a distributed file upload verification method, device, equipment and storage medium. Background Art

[0002] In the modern information society, the amount of data has increased dramatically, especially driven by big data and cloud computing technologies, and the demand for uploading various types of files has also increased significantly. Distributed file storage systems (DFS) have become an important tool for managing and storing large amounts of data. However, existing distributed file storage systems still face many technical challenges and problems in the file uploading process.

[0003] In a distributed file storage system, the file upload process is easily affected by the network environment. For example, factors such as network delays, bandwidth limitations, and network congestion can lead to unstable data transmission speeds, or even data loss or corruption. These problems are particularly prominent during large file uploads, which may result in extended file upload times or even upload failures.

[0004] Due to the uncertainty of network transmission, "packet loss" may occur during the file upload process, that is, some data blocks are lost or damaged during the transmission process, resulting in incomplete files. This situation not only affects the user experience, but may also cause the loss or damage of important data, and in serious cases may cause data security issues.

[0005] Most existing distributed file storage systems lack effective real-time monitoring and feedback mechanisms, and are unable to monitor data integrity issues in the file upload process in a timely manner. When users upload files, they can only know whether the file has been successfully uploaded and whether it is complete after the upload is completed. This lagging feedback mechanism cannot meet users' needs for real-time and reliability.

[0006] Due to the possibility of data loss or corruption during the upload process, existing systems usually re-upload the entire file or a large number of data blocks when re-uploading data, resulting in increased data redundancy and storage costs. In addition, the lack of an intelligent judgment mechanism makes it impossible to effectively distinguish between data blocks that need to be re-uploaded and data blocks that have been successfully uploaded, further increasing storage and transmission costs. Summary of the invention

[0007] The main purpose of the present invention is to provide a distributed file upload verification method, device, equipment and storage medium, aiming to solve the technical problem that it is difficult to ensure data integrity during the file upload process in the prior art.

[0008] To achieve the above object, the present invention provides a distributed file upload verification method, which comprises the following steps:

[0009] Obtain a file to be uploaded, split the file to be uploaded into multiple data blocks according to a preset threshold, upload the multiple data blocks to a distributed file system, obtain upload information of each data block through the distributed file system, and store the upload information of each data block in an Uploading linked list;

[0010] Integrate the upload information in the Uploading linked list to obtain integrated data, wherein the integrated data includes the upload information of each data block, and upload the integrated data to the Upload-Result linked list;

[0011] monitoring the integrated data of the Upload-Result linked list in real time, and when detecting the existence of a successfully uploaded data block, comparing the successfully uploaded data block through the distributed file system;

[0012] If the successfully uploaded data block has an abnormality, the user is prompted that the upload is abnormal; if all of the multiple data blocks have no abnormalities, the user is prompted that the upload is successful.

[0013] Optionally, after the step of if the successfully uploaded data block has an abnormality, the method further includes:

[0014] The abnormal data blocks are deleted from the distributed file system.

[0015] Optionally, after the step of real-time monitoring the integrated data of the Upload-Result linked list, the method further includes:

[0016] When it is detected that there is a data block that fails to be uploaded, the data block that fails to be uploaded is marked and the data block that fails to be uploaded is deleted from the distributed file system.

[0017] Optionally, after the step of prompting the user that the upload is abnormal if the successfully uploaded data block has an abnormality; and prompting the user that the upload is successful if none of the multiple data blocks has an abnormality, the method further includes:

[0018] Integrate all successfully uploaded data block information into the Monitor-Result linked list. When the user re-uploads the file to be uploaded, determine the data blocks to be uploaded that need to be re-uploaded according to the Monitor-Result linked list, and upload the data blocks to be uploaded to the distributed file system;

[0019] If the data block to be uploaded is uploaded successfully, the user is prompted that the upload is successful.

[0020] Optionally, after the step of integrating all successfully uploaded data block information into the Monitor-Result linked list, the method further includes:

[0021] The upload information corresponding to all successfully uploaded data block information is deleted from the Upload-Result linked list.

[0022] Optionally, after the step of successfully uploading the data block to be uploaded, the method further includes:

[0023] All successfully uploaded data block information in the Monitor-Result linked list is persistently stored in the database. If the persistent storage is successful, the persistently stored data block information in the Monitor-Result linked list is deleted.

[0024] Optionally, the step of uploading the multiple data blocks to a distributed file system includes:

[0025] The multiple data blocks are uploaded to the distributed file system in a multi-threaded uploading manner.

[0026] Furthermore, to achieve the above-mentioned purpose, the present invention also provides a distributed file upload verification device, the distributed file upload verification device comprising:

[0027] A file splitting and uploading module, which obtains a file to be uploaded, splits the file to be uploaded into multiple data blocks according to a preset threshold, uploads the multiple data blocks to a distributed file system, obtains upload information of each data block through the distributed file system, and stores the upload information of each data block in an Uploading linked list;

[0028] An upload information integration module integrates the upload information in the Uploading linked list to obtain integrated data, wherein the integrated data includes the upload information of each data block, and uploads the integrated data to the Upload-Result linked list;

[0029] An upload status monitoring module monitors the integrated data of the Upload-Result linked list in real time, and when a successfully uploaded data block is detected, compares the successfully uploaded data block through the distributed file system;

[0030] The verification result prompt module prompts the user that the upload is abnormal if there is an abnormality in the successfully uploaded data block; if there is no abnormality in all the multiple data blocks, prompts the user that the upload is successful.

[0031] Furthermore, to achieve the above-mentioned purpose, the present invention also provides a distributed file upload verification device, which includes a memory, a processor, and a distributed file upload verification program stored in the memory and executable on the processor, and the distributed file upload verification program, when executed by the processor, implements the steps of the distributed file upload verification method described above.

[0032] Furthermore, to achieve the above-mentioned purpose, the present invention also provides a storage medium, on which a distributed file upload verification program is stored, and when the distributed file upload verification program is executed by a processor, the steps of the distributed file upload verification method as described above are implemented.

[0033] The present invention relates to a distributed file upload verification method, which comprises the following steps: obtaining a file to be uploaded, splitting the file to be uploaded into multiple data blocks according to a preset threshold, and uploading the multiple data blocks to a distributed file system; obtaining upload information of each data block through the distributed file system, and storing the upload information of each data block in an Uploading chain table; integrating the upload information in the Uploading chain table to obtain integrated data, wherein the integrated data includes the upload information of each data block, and uploading the integrated data to an Upload-Result chain table; monitoring the integrated data of the Upload-Result chain table in real time, and comparing the successfully uploaded data blocks through a distributed file system when monitoring the existence of successfully uploaded data blocks; if the successfully uploaded data blocks are abnormal, prompting a user to upload abnormalities; and prompting a user to upload successfully if all the multiple data blocks are not abnormal. The present invention ensures the integrity and accuracy of data by real-time monitoring and verifying the upload status of each data block. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 It is a schematic diagram of the structure of the device hardware operating environment involved in the embodiment of the distributed file upload verification device of the present invention;

[0035] Figure 2 This is a flow chart of a first embodiment of a distributed file upload verification method of the present invention;

[0036] Figure 3 It is a functional module diagram of a preferred embodiment of the distributed file upload verification device of the present invention.

[0037] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0038] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.

[0039] It should be noted that in the modern information society, the amount of data has increased dramatically, especially driven by big data and cloud computing technologies, and the demand for uploading various types of files has also increased significantly. Distributed file storage system (DFS) has become an important tool for managing and storing large amounts of data. However, existing distributed file storage systems still face many technical challenges and problems in the file uploading process.

[0040] In a distributed file storage system, the file upload process is easily affected by the network environment. For example, factors such as network delays, bandwidth limitations, and network congestion can lead to unstable data transmission speeds, or even data loss or corruption. These problems are particularly prominent during large file uploads, which may result in extended file upload times or even upload failures.

[0041] Due to the uncertainty of network transmission, "packet loss" may occur during the file upload process, that is, some data blocks are lost or damaged during the transmission process, resulting in incomplete files. This situation not only affects the user experience, but may also cause the loss or damage of important data, and in serious cases may cause data security issues.

[0042] Most existing distributed file storage systems lack effective real-time monitoring and feedback mechanisms, and are unable to monitor data integrity issues in the file upload process in a timely manner. When users upload files, they can only know whether the file has been successfully uploaded and whether it is complete after the upload is completed. This lagging feedback mechanism cannot meet users' needs for real-time and reliability.

[0043] Due to the possibility of data loss or corruption during the upload process, existing systems usually re-upload the entire file or a large number of data blocks when re-uploading data, resulting in increased data redundancy and storage costs. In addition, the lack of an intelligent judgment mechanism makes it impossible to effectively distinguish between data blocks that need to be re-uploaded and data blocks that have been successfully uploaded, further increasing storage and transmission costs.

[0044] Based on the above defects, the present invention provides a distributed file upload verification device, referring to Figure 1 , Figure 1 It is a structural schematic diagram of the device hardware operating environment involved in the embodiment of the distributed file upload verification device of the present invention.

[0045] like Figure 1As shown, the distributed file upload verification device may include: a processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory, or it may be a stable memory (non-volatile memory), such as a disk memory. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0046] Those skilled in the art will understand that Figure 1 The hardware structure of the distributed file upload verification device shown in the figure does not constitute a limitation on the distributed file upload verification device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0047] like Figure 1 As shown, the memory 1005 as a storage medium may include an operating system, a network communication module, a user interface module, and a distributed file upload verification program. The operating system is a program for managing and controlling the distributed file upload verification device and software resources, and supports the operation of the network communication module, the user interface module, the distributed file upload verification program, and other programs or software; the network communication module is used to manage and control the network interface 1004; and the user interface module is used to manage and control the user interface 1003.

[0048] exist Figure 1 In the hardware structure of the distributed file upload verification device shown, the network interface 1004 is mainly used to connect to the background server and communicate data with the background server; the user interface 1003 is mainly used to connect to the client and communicate data with the client; the processor 1001 can call the distributed file upload verification program stored in the memory 1005 and perform the following operations:

[0049] Obtain a file to be uploaded, split the file to be uploaded into multiple data blocks according to a preset threshold, upload the multiple data blocks to a distributed file system, obtain upload information of each data block through the distributed file system, and store the upload information of each data block in an Uploading linked list;

[0050] Integrate the upload information in the Uploading linked list to obtain integrated data, wherein the integrated data includes the upload information of each data block, and upload the integrated data to the Upload-Result linked list;

[0051] monitoring the integrated data of the Upload-Result linked list in real time, and when detecting the existence of a successfully uploaded data block, comparing the successfully uploaded data block through the distributed file system;

[0052] If the successfully uploaded data block has an abnormality, the user is prompted that the upload is abnormal; if all of the multiple data blocks have no abnormalities, the user is prompted that the upload is successful.

[0053] Furthermore, after the step of if the successfully uploaded data block has an abnormality, the method further includes:

[0054] The abnormal data blocks are deleted from the distributed file system.

[0055] Furthermore, after the step of real-time monitoring the integrated data of the Upload-Result linked list, the method further includes:

[0056] When it is detected that there is a data block that fails to be uploaded, the data block that fails to be uploaded is marked and the data block that fails to be uploaded is deleted from the distributed file system.

[0057] Furthermore, after the step of prompting the user that the upload is abnormal if the successfully uploaded data block has an abnormality, and prompting the user that the upload is successful if none of the multiple data blocks have an abnormality, the method further includes:

[0058] Integrate all successfully uploaded data block information into the Monitor-Result linked list. When the user re-uploads the file to be uploaded, determine the data blocks to be uploaded that need to be re-uploaded according to the Monitor-Result linked list, and upload the data blocks to be uploaded to the distributed file system;

[0059] If the data block to be uploaded is uploaded successfully, the user is prompted that the upload is successful.

[0060] Furthermore, after the step of integrating all successfully uploaded data block information into the Monitor-Result linked list, the following step is further included:

[0061] The upload information corresponding to all successfully uploaded data block information is deleted from the Upload-Result linked list.

[0062] Furthermore, after the step of successfully uploading the data block to be uploaded, the method further includes:

[0063] All successfully uploaded data block information in the Monitor-Result linked list is persistently stored in the database. If the persistent storage is successful, the persistently stored data block information in the Monitor-Result linked list is deleted.

[0064] Furthermore, the step of uploading the plurality of data blocks to a distributed file system includes:

[0065] The multiple data blocks are uploaded to the distributed file system in a multi-threaded uploading manner.

[0066] The specific implementation of the distributed file upload verification device of the present invention is basically the same as the embodiments of the distributed file upload verification method described below, and will not be repeated here.

[0067] The present invention also provides a distributed file upload verification method based on the above-mentioned distributed file upload verification device.

[0068] Reference Figure 2 , Figure 2 It is a flowchart of the first embodiment of the distributed file upload verification method of the present invention.

[0069] The embodiment of the present invention provides an embodiment of a distributed file upload verification method. It should be noted that although the logical order is shown in the flow chart, in some cases, the steps shown or described may be executed in an order different from that here.

[0070] In various embodiments of the distributed file upload verification method, the execution subject is a distributed file upload verification device.

[0071] The distributed file upload verification method is applied to a distributed file upload verification device, and the distributed file upload verification method includes:

[0072] Step S10, obtaining a file to be uploaded, splitting the file to be uploaded into multiple data blocks according to a preset threshold, uploading the multiple data blocks to a distributed file system, obtaining upload information of each data block through the distributed file system, and storing the upload information of each data block in an Uploading linked list;

[0073] In the modern information society, the amount of data has increased dramatically, especially driven by big data and cloud computing technologies, and the demand for uploading various types of files has also increased significantly. Distributed file storage systems (DFS) have become an important tool for managing and storing large amounts of data. However, existing distributed file storage systems still face many technical challenges and problems in the file uploading process.

[0074] In a distributed file storage system, the file upload process is easily affected by the network environment. For example, factors such as network delays, bandwidth limitations, and network congestion can lead to unstable data transmission speeds, or even data loss or corruption. These problems are particularly prominent during large file uploads, which may result in extended file upload times or even upload failures.

[0075] Due to the uncertainty of network transmission, "packet loss" may occur during the file upload process, that is, some data blocks are lost or damaged during the transmission process, resulting in incomplete files. This situation not only affects the user experience, but may also cause the loss or damage of important data, and in serious cases may cause data security issues.

[0076] Most existing distributed file storage systems lack effective real-time monitoring and feedback mechanisms, and are unable to monitor data integrity issues in the file upload process in a timely manner. When users upload files, they can only know whether the file has been successfully uploaded and whether it is complete after the upload is completed. This lagging feedback mechanism cannot meet users' needs for real-time and reliability.

[0077] Due to the possibility of data loss or corruption during the upload process, existing systems usually re-upload the entire file or a large number of data blocks when re-uploading data, resulting in increased data redundancy and storage costs. In addition, the lack of an intelligent judgment mechanism makes it impossible to effectively distinguish between data blocks that need to be re-uploaded and data blocks that have been successfully uploaded, further increasing storage and transmission costs.

[0078] In this embodiment, the user selects a file to be uploaded through the client. The file can be any type of file, such as a document, a picture, a video, etc. Inside the system, the file to be uploaded is loaded into the memory and prepared for processing.

[0079] The file to be uploaded is split into several data blocks according to the preset threshold. The preset threshold can be set according to factors such as network bandwidth and file size. Assuming the preset threshold is 20MB, a 100MB file will be split into 5 data blocks.

[0080] The split data blocks are uploaded to the distributed file system (DFS) in parallel through multi-threading. Multi-threaded uploading can make full use of network bandwidth and system resources and improve uploading efficiency. Each thread is responsible for uploading one or more data blocks.

[0081] After each data block is uploaded to DFS, the system will return the upload status information of the data block, including whether the upload is successful, storage location, data block size, etc. This information is used for subsequent verification and management.

[0082] The upload information of each data block is stored in a temporary linked list (Uploading linked list) for unified management and subsequent processing. The Uploading linked list records the upload status information of all data blocks.

[0083] Through the above steps, the system can effectively split large files and upload them to the distributed file system, while ensuring that the upload status and information of each data block are accurately recorded and managed, ensuring the data integrity and reliability during the file upload process.

[0084] Example description:

[0085] Get the file to be uploaded: The user selects a file named large_file.zip on the client, which is 100MB in size. The system loads large_file.zip into memory and prepares to process it.

[0086] Split file: The preset threshold is 20MB. The system splits large_file.zip into 5 data blocks according to the 20MB threshold:

[0087] Data block 1: large_file_part1.zip, size 20MB

[0088] Data block 2: large_file_part2.zip, size 20MB

[0089] Data block 3: large_file_part3.zip, size 20MB

[0090] Data block 4: large_file_part4.zip, size 20MB

[0091] Data block 5: large_file_part5.zip, size 20MB

[0092] Multi-threaded data block upload: The system starts 5 threads, each of which is responsible for uploading a data block to DFS. Thread 1 uploads large_file_part1.zip, thread 2 uploads large_file_part2.zip, and so on. After each thread completes uploading, the system obtains the upload status information of the data block from DFS.

[0093] Get upload information: For example, if large_file_part1.zip is uploaded successfully, the returned information includes:

[0094] Upload Status: Success

[0095] Storage location: dfs: / / path / to / large_file_part1.zip

[0096] Data block size: 20MB

[0097] Storing upload information in the Uploading list: The system stores the upload information of each data block in the Uploading list:

[0098] Uploading list:

[0099] -Data block 1: upload status (success), storage location (dfs: / / path / to / large_file_part1.zip), size (20MB);

[0100] -Data block 2: upload status (success), storage location (dfs: / / path / to / large_file_part2.zip), size (20MB);

[0101] -Data block 3: upload status (success), storage location (dfs: / / path / to / large_file_part3.zip), size (20MB);

[0102] -Data block 4: upload status (success), storage location (dfs: / / path / to / large_file_part4.zip), size (20MB);

[0103] -Data block 5: upload status (success), storage location (dfs: / / path / to / large_file_part5.zip), size (20MB).

[0104] Step S20, integrating the upload information in the Uploading linked list to obtain integrated data, wherein the integrated data includes the upload information of each data block, and uploading the integrated data to the Upload-Result linked list;

[0105] In this embodiment, the Uploading linked list stores the upload information of each data block, including the upload status, storage location, data block size, etc. The system first obtains the upload information from the Uploading linked list.

[0106] The upload information in the Uploading list is integrated to generate an integrated data structure containing all data block upload information. The integrated data contains detailed upload information of each data block, such as upload status, storage location, data block size, etc.

[0107] After the integrated data is generated, the system uploads it to the Upload-Result linked list. The Upload-Result linked list is used to store the complete upload information of all data blocks for subsequent real-time monitoring and verification.

[0108] Through the above steps, the upload information of all data blocks can be effectively integrated and managed to ensure the data integrity and reliability during the file upload process, while providing comprehensive data support for subsequent monitoring and verification.

[0109] Example description:

[0110] Get the upload information in the Uploading list: The system reads the upload information of each data block from the Uploading list. Assume that the Uploading list records that the file "large_file.zip" is split into 5 data blocks, and the upload information of each data block is as follows:

[0111] Data block 1: upload status (success), storage location (path in the distributed file system), size (20MB);

[0112] Data block 2: upload status (success), storage location (path in the distributed file system), size (20MB);

[0113] Data block 3: upload status (success), storage location (path in the distributed file system), size (20MB);

[0114] Data block 4: upload status (success), storage location (path in the distributed file system), size (20MB);

[0115] Data block 5: upload status (success), storage location (path in the distributed file system), size (20MB).

[0116] Integrate the uploaded information: The system integrates the uploaded information in the Uploading list to generate an integrated data structure containing detailed information of all data blocks:

[0117] {

[0118] "File name":"large_file.zip",

[0119] "Data block information":[

[0120] {"Data block":1,"Upload status":"Success","Storage location":"dfs: / / path / to / large_file_part1.zip","Size":"20MB"},

[0121] {"Data block":2,"Upload status":"Success","Storage location":"dfs: / / path / to / large_file_part2.zip","Size":"20MB"},

[0122] {"Data block":3,"Upload status":"Success","Storage location":"dfs: / / path / to / large_file_part3.zip","Size":"20MB"},

[0123] {"Data block":4,"Upload status":"Success","Storage location":"dfs: / / path / to / large_file_part4.zip","Size":"20MB"},

[0124] {"Data block":5,"Upload status":"Success","Storage location":"dfs: / / path / to / large_file_part5.zip","Size":"20MB"} ]

[0126] }

[0127] Upload the integrated data to the Upload-Result linked list.

[0128] Step S30, monitoring the integrated data of the Upload-Result linked list in real time, and when detecting the existence of a successfully uploaded data block, comparing the successfully uploaded data block through the distributed file system;

[0129] In this embodiment, the system continuously monitors the integrated data in the Upload-Result linked list to ensure that the upload status of each data block can be checked and processed in a timely manner. For example, the Upload-Result linked list records the upload information of each data block of the file "large_file.zip". The system continuously monitors the linked list to check the upload status of each data block, paying special attention to the data blocks that have been successfully uploaded.

[0130] Assume that the system detects that there are successfully uploaded data blocks in the Upload-Result linked list, such as data block 1, data block 2, and data block 3. The system marks these data blocks as "pending verification" and records their storage location, size, and other detailed information. For example:

[0131] Data block 1: status (to be verified), storage location (path in the distributed file system), size (20MB);

[0132] Data block 2: status (to be verified), storage location (path in the distributed file system), size (20MB);

[0133] Data block 3: status (to be verified), storage location (path in the distributed file system), size (20MB).

[0134] The system reads the data block information marked as "to be verified" from the Upload-Result linked list and compares it through the distributed file system.

[0135] The comparison operation includes: verifying the integrity of the data block to ensure that the data block has not been modified or damaged; verifying the consistency of the data block to ensure that the uploaded data block is consistent with the original data block.

[0136] After the comparison is successful, the system updates the status of the data block to "verification successful". If any abnormality is found, the user will be prompted and corresponding processing will be performed.

[0137] Through the above steps, each successfully uploaded data block can be effectively monitored and verified to ensure the data integrity and reliability during the file upload process, while providing comprehensive data support for subsequent exception handling.

[0138] Example description:

[0139] Real-time monitoring of the Upload-Result chain table: The system monitors the integrated data in the Upload-Result chain table in real time. Assume that the Upload-Result chain table records the upload information of each data block of the file "large_file.zip".

[0140] Detecting successfully uploaded data blocks: The system detects that there are successfully uploaded data blocks in the Upload-Result linked list, such as data block 1, data block 2, and data block 3. The system marks these data blocks as "pending verification" and records detailed information such as their storage location and size.

[0141] Comparison through the distributed file system: The system reads the data block information marked as "to be verified" from the Upload-Result linked list and compares it through the distributed file system. The comparison operation includes verifying the integrity and consistency of the data block to ensure that the uploaded data block is consistent with the original data block. After the comparison is successful, the system updates the status of the data block to "verification successful". If an abnormality is found, the user is prompted and the corresponding processing is performed.

[0142] Step S40: If the successfully uploaded data block has an abnormality, the user is prompted that the upload is abnormal; if none of the multiple data blocks have an abnormality, the user is prompted that the upload is successful.

[0143] In this embodiment, the system checks the integrity and consistency of each successfully uploaded data block during the comparison process. For example, the file "large_file.zip" is split into 5 data blocks, and the system compares these data blocks one by one.

[0144] Assume that when the system compares data block 1, data block 2, and data block 3, it confirms that they are all normal. When comparing data block 4, the system detects that the data block has an abnormality, such as the data block is incomplete or inconsistent with the original data. The system records the abnormality and prompts the user to upload the abnormality. For example, the prompt message can be: "Data block 4 upload abnormality, please re-upload the data block."

[0145] When comparing data block 5, the system confirms that there is no abnormality in the data block. Because the system detected an abnormality in data block 4 during the comparison process, the system will not prompt that the upload is successful, but wait for the user to process the abnormal data block.

[0146] If the system confirms that all successfully uploaded data blocks are normal (for example, after the user re-uploads data block 4 and confirms that there are no abnormalities), the system will prompt the user that the upload is successful. The prompt message can be: "The file large_file.zip has been successfully uploaded, and all data blocks are normal."

[0147] Through the above steps, each successfully uploaded data block can be effectively processed and verified to ensure the data integrity and reliability during the file upload process, and prompt the user to take measures in time when an abnormality occurs, ultimately ensuring that the file is successfully uploaded and the data is complete.

[0148] Example description:

[0149] Check the data blocks uploaded successfully: During the comparison process, the system checks the 5 data blocks of the file "large_file.zip". During the comparison process, the system confirms that there are no abnormalities in data blocks 1, 2, and 3.

[0150] Processing abnormal data blocks: When comparing data block 4, the system detects that the data block is abnormal (such as incomplete data or inconsistent with the original data). The system records the abnormality and prompts the user: "Data block 4 upload abnormality, please re-upload the data block."

[0151] Confirm that all data blocks are normal: When comparing data block 5, the system confirms that the data block is normal. Since data block 4 is abnormal, the system will not prompt that the upload is successful, but wait for the user to process the abnormal data block.

[0152] The user is prompted that the upload is successful: After the user re-uploads data block 4, the system re-checks and confirms that there are no abnormalities. At this time, the system prompts the user: "The file large_file.zip has been successfully uploaded, and all data blocks are normal."

[0153] The present invention relates to a distributed file upload verification method, which comprises the following steps: obtaining a file to be uploaded, splitting the file to be uploaded into multiple data blocks according to a preset threshold, and uploading the multiple data blocks to a distributed file system; obtaining upload information of each data block through the distributed file system, and storing the upload information of each data block in an Uploading chain table; integrating the upload information in the Uploading chain table to obtain integrated data, wherein the integrated data includes the upload information of each data block, and uploading the integrated data to an Upload-Result chain table; monitoring the integrated data of the Upload-Result chain table in real time, and comparing the successfully uploaded data blocks through a distributed file system when monitoring the existence of successfully uploaded data blocks; if the successfully uploaded data blocks are abnormal, prompting a user to upload abnormalities; and prompting a user to upload successfully if all the multiple data blocks are not abnormal. The present invention ensures the integrity and accuracy of data by real-time monitoring and verifying the upload status of each data block.

[0154] Furthermore, a second embodiment of the distributed file upload verification method of the present invention is proposed. In the above step S40, after the step of if the successfully uploaded data block has an abnormality, the method further includes:

[0155] Step a1: deleting abnormal data blocks from the distributed file system.

[0156] In this embodiment, when comparing data blocks, the system checks the integrity and consistency of each successfully uploaded data block. If an abnormality is found in the data block (for example, the data block is incomplete or inconsistent with the original data), the system will record the abnormality.

[0157] When an abnormality is detected in a successfully uploaded data block, the system will delete the abnormal data block from the distributed file system to ensure the accuracy and integrity of the data.

[0158] The system records the exception and prompts the user to upload the exception, informing the user that the data block with the exception needs to be re-uploaded.

[0159] Example description:

[0160] Check the data blocks uploaded successfully: During the comparison process, the system checks the 5 data blocks of the file "large_file.zip". During the comparison process, the system confirms that there are no abnormalities in data blocks 1, 2, and 3.

[0161] Processing abnormal data blocks: When comparing data block 4, the system detects that the data block is abnormal (such as incomplete data or inconsistent with the original data). The system records the abnormality and decides to delete data block 4.

[0162] Deleting abnormal data blocks: The system deletes the storage record of data block 4 through the API or management interface of the distributed file system. This operation ensures that data block 4 no longer exists in the distributed file system.

[0163] Prompt the user of upload exception: The system records the exception and prompts the user: "Data block 4 upload exception, has been deleted from the distributed file system, please upload the data block again."

[0164] Through the above steps, this embodiment can effectively process and delete abnormal data blocks, ensure the accuracy and integrity of data in the distributed file system, and promptly prompt the user to re-upload the abnormal data blocks to ensure that the file is finally uploaded completely.

[0165] Furthermore, a third embodiment of the distributed file upload verification method of the present invention is proposed. In the above step S30, after the step of real-time monitoring of the integrated data of the Upload-Result linked list, the method further includes:

[0166] Step b1: when it is detected that there is a data block that fails to be uploaded, the data block that fails to be uploaded is marked, and the data block that fails to be uploaded is deleted from the distributed file system.

[0167] In this embodiment, the system monitors the integrated data in the Upload-Result linked list in real time. For example, the Upload-Result linked list records the upload information of each data block of the file "large_file.zip". The system continuously monitors the linked list, checks the upload status of each data block, and pays special attention to whether there are data blocks that fail to upload.

[0168] Assume that the system detects that there are data blocks in the Upload-Result linked list that failed to be uploaded, such as data blocks 4 and 5. The system marks these data blocks as "failed to upload" and records their storage location, size and other detailed information. For example:

[0169] Data block 4: status (upload failed), storage location (path in the distributed file system), size (20MB);

[0170] Data block 5: status (upload failed), storage location (path in the distributed file system), size (20MB).

[0171] The system deletes the data blocks marked as "failed to upload" through the API or management interface of the distributed file system. The system deletes the storage records of data blocks 4 and 5 to ensure that these data blocks that failed to upload no longer exist in the distributed file system.

[0172] Example description:

[0173] Real-time monitoring of the integrated data in the Upload-Result chain table: The system monitors the integrated data in the Upload-Result chain table in real time. Assume that the Upload-Result chain table records the upload information of each data block of the file "large_file.zip".

[0174] Marking data blocks that failed to upload: The system detects data blocks that failed to upload in the Upload-Result list, such as data blocks 4 and 5. The system marks these data blocks as "failed to upload" and records detailed information such as their storage location and size.

[0175] Delete data blocks that failed to upload: The system deletes data blocks marked as "failed to upload" through the API or management interface of the distributed file system. The system deletes the storage records of data blocks 4 and 5 to ensure that these data blocks that failed to upload no longer exist in the distributed file system.

[0176] Through the above steps, this embodiment can effectively monitor and process data blocks that fail to be uploaded, ensure the accuracy and integrity of data in the distributed file system, and avoid data redundancy and waste of storage space.

[0177] Furthermore, a fourth embodiment of the distributed file upload verification method of the present invention is proposed, after the above step S40, it also includes:

[0178] Step c1, integrating all successfully uploaded data block information into the Monitor-Result linked list. When the user re-uploads the file to be uploaded, the data block to be uploaded that needs to be re-uploaded is determined according to the Monitor-Result linked list, and the data block to be uploaded is uploaded to the distributed file system;

[0179] Step c2: If the data block to be uploaded is uploaded successfully, the user is prompted that the upload is successful.

[0180] In this embodiment, the system detects the integrity and consistency of each successfully uploaded data block to confirm whether there is an abnormality. If there is an abnormality, the user is prompted to upload the abnormality; if all data blocks are normal, the user is prompted to upload successfully.

[0181] After confirming that all successfully uploaded data blocks are normal, the system integrates the information of these data blocks into the Monitor-Result linked list. The Monitor-Result linked list is used to record the information of all successfully uploaded data blocks for subsequent monitoring and processing.

[0182] When the user re-uploads the file to be uploaded, the system determines the data blocks to be uploaded that need to be re-uploaded according to the Monitor-Result linked list, and uploads these data blocks to the distributed file system.

[0183] If the data block to be uploaded is successfully re-uploaded, the system will prompt the user that the upload is successful.

[0184] Example description:

[0185] Detect and process successfully uploaded data blocks: The system compares the five data blocks of the file "large_file.zip" and finds that data block 4 is abnormal. The user is prompted to re-upload the data block.

[0186] Integrate the successful data block information into the Monitor-Result linked list: The system confirms that there are no abnormalities in data block 1, data block 2, data block 3 and data block 5, and integrates the information of these data blocks into the Monitor-Result linked list.

[0187] The user re-uploads the abnormal data block: When the user re-uploads the file "large_file.zip", the system determines the data block 4 that needs to be re-uploaded according to the Monitor-Result linked list.

[0188] Confirm the re-uploaded data block: The system confirms that data block 4 has been re-uploaded successfully and there are no abnormalities. The system adds the information of data block 4 to the Monitor-Result linked list and prompts the user that the upload is successful.

[0189] Through the above steps, this embodiment can effectively process and verify each successfully uploaded data block, ensure the data integrity and reliability during the file upload process, and promptly prompt the user to take measures when an abnormality occurs, ultimately ensuring that the file is successfully uploaded and the data is complete.

[0190] Furthermore, a fifth embodiment of the distributed file upload verification method of the present invention is proposed. In the above step c1, after the step of integrating the information of all successfully uploaded data blocks into the Monitor-Result linked list, the method further includes:

[0191] Step d1, deleting the upload information corresponding to all successfully uploaded data block information from the Upload-Result linked list.

[0192] In this embodiment, the system integrates all successfully uploaded data block information from the Upload-Result linked list into the Monitor-Result linked list, ensuring that the successful data block information is uniformly recorded and managed.

[0193] After successfully integrating the data block information into the Monitor-Result linked list, the system will delete the corresponding upload information from the Upload-Result linked list to prevent data redundancy and confusion, ensuring that only the data block information that needs further processing is retained in the linked list.

[0194] Example description:

[0195] The system confirms that data blocks 1, 2, 3, and 5 of the file "large_file.zip" have been uploaded successfully and without exception. The system integrates the information of these data blocks from the Upload-Result linked list into the Monitor-Result linked list. For example:

[0196] Monitor-Result linked list:

[0197] - File name: large_file.zip

[0198] -Data block 1: status (success), storage location (dfs: / / path / to / large_file_part1.zip), size (20MB);

[0199] -Data block 2: status (success), storage location (dfs: / / path / to / large_file_part2.zip), size (20MB);

[0200] -Data block 3: status (success), storage location (dfs: / / path / to / large_file_part3.zip), size (20MB);

[0201] -Data block 5: status (success), storage location (dfs: / / path / to / large_file_part5.zip), size (20MB).

[0202] Delete successful data block information from the Upload-Result chain list: After the system integrates the successful data block information into the Monitor-Result chain list, it deletes the successful data block information from the Upload-Result chain list. For example:

[0203] Upload-Result linked list (updated):

[0204] - File name: large_file.zip;

[0205] -Data block 4: status (failed), storage location (dfs: / / path / to / large_file_part4.zip), size (20MB).

[0206] Through the above steps, this embodiment can effectively integrate and manage the successfully uploaded data block information, and delete the successfully uploaded information in the Upload-Result linked list, thereby ensuring the accuracy and simplicity of data records.

[0207] Furthermore, a sixth embodiment of the distributed file upload verification method of the present invention is proposed. In the above step c2, after the step of if the data block to be uploaded is uploaded successfully, the method further includes:

[0208] Step e1, persistently storing all successfully uploaded data block information in the Monitor-Result linked list in a database. If the persistent storage is successful, delete the persistently stored data block information in the Monitor-Result linked list.

[0209] In this embodiment, the user re-uploads a data block of the file. The system confirms that the data block is successfully re-uploaded, and performs a comparison check to ensure that there is no abnormality in the data block. The system updates the information of the data block to the Monitor-Result linked list.

[0210] The system stores all successfully uploaded data block information recorded in the Monitor-Result linked list in a persistent manner in the database. For example, the information of all data blocks of a file is stored in the database.

[0211] After the system confirms that the data block information has been successfully persisted and stored in the database, it deletes the successful data block information from the Monitor-Result linked list.

[0212] Example description:

[0213] Confirm that the data block to be uploaded is uploaded successfully: The user re-uploads a data block of the file. The system confirms that the data block is uploaded successfully and there is no abnormality, and updates its information to the Monitor-Result linked list.

[0214] Persistent storage of successful data block information: The system persistently stores all successfully uploaded data block information in the Monitor-Result linked list in the database to ensure that the information of these data blocks is preserved and managed for a long time.

[0215] Delete the successful data block information in the Monitor-Result linked list: After the system confirms that the data block information has been successfully persisted and stored in the database, delete the successful data block information from the Monitor-Result linked list to ensure that only the information that needs further processing is retained in the linked list.

[0216] Through the above steps, this embodiment can effectively manage the successfully uploaded data block information, ensure the long-term preservation and management of data, and maintain the simplicity and accuracy of the Monitor-Result chain table.

[0217] Furthermore, a seventh embodiment of the distributed file upload verification method of the present invention is proposed. In the above step S10, the step of uploading the multiple data blocks to the distributed file system includes:

[0218] Step f1, uploading the multiple data blocks to the distributed file system by adopting a multi-threaded uploading method.

[0219] In this embodiment, the file to be uploaded is first split into multiple data blocks according to a preset threshold value. These data blocks will be uploaded in parallel in subsequent steps.

[0220] In order to improve the upload efficiency, the system adopts multi-threaded upload to upload multiple data blocks to the distributed file system in parallel. Each thread is responsible for uploading one or more data blocks. The use of multi-threading technology can maximize the use of network bandwidth and system resources.

[0221] When uploading a data block, each thread will record the upload status and related information in real time, such as the storage location of the data block, upload status, data block size, etc. This information will be stored in the Uploading list for subsequent integration and monitoring.

[0222] Example description:

[0223] Data block splitting: The user selected the file "large_file.zip". The system split it into 5 data blocks, each of which is 20 MB.

[0224] Multi-threaded upload: The system starts 5 threads:

[0225] Thread 1 uploads data block 1.

[0226] Thread 2 uploads data block 2.

[0227] Thread 3 uploads data block 3.

[0228] Thread 4 uploads data block 4.

[0229] Thread 5 uploads data block 5.

[0230] Each thread uploads data blocks to the distributed file system in parallel.

[0231] Upload information record:

[0232] Thread 1 successfully uploads data block 1 and records the storage location, upload status, and size of data block 1.

[0233] Thread 2 successfully uploads data block 2 and records the storage location, upload status, and size of data block 2.

[0234] Similarly, the upload information of all data blocks is stored in the Uploading list.

[0235] Through the above steps, this embodiment can effectively utilize multi-threading technology to improve the efficiency of file uploading and ensure that the uploaded information of each data block is accurately recorded and managed, providing data support for subsequent integration and monitoring.

[0236] The invention also provides a distributed file upload verification device.

[0237] Reference Figure 3 , Figure 3 This is a functional module diagram of the first embodiment of the distributed file upload verification device of the present invention. The distributed file upload verification device comprises:

[0238] A file splitting and uploading module, which obtains a file to be uploaded, splits the file to be uploaded into multiple data blocks according to a preset threshold, uploads the multiple data blocks to a distributed file system, obtains upload information of each data block through the distributed file system, and stores the upload information of each data block in an Uploading linked list;

[0239] An upload information integration module integrates the upload information in the Uploading linked list to obtain integrated data, wherein the integrated data includes the upload information of each data block, and uploads the integrated data to the Upload-Result linked list;

[0240] An upload status monitoring module monitors the integrated data of the Upload-Result linked list in real time, and when a successfully uploaded data block is detected, compares the successfully uploaded data block through the distributed file system;

[0241] The verification result prompt module prompts the user that the upload is abnormal if there is an abnormality in the successfully uploaded data block; if there is no abnormality in all the multiple data blocks, prompts the user that the upload is successful.

[0242] In addition, an embodiment of the present invention further provides a storage medium.

[0243] A distributed file upload verification program is stored on the storage medium, and when the distributed file upload verification program is executed by the processor, the steps of the distributed file upload verification method as described above are implemented.

[0244] The specific implementation of the storage medium of the present invention is basically the same as the above-mentioned embodiments of the distributed file upload verification method, and will not be repeated here.

[0245] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the enlightenment of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims. All equivalent structures or equivalent process changes made using the contents of the specification and drawings of the present invention, or directly or indirectly used in other related technical fields, are protected by the present invention.

[0246] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to the multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or the flowchart, and the combination of boxes in the block diagram and / or the flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0247] In addition, each functional module in each embodiment of the present application can be integrated together to form an independent part, or each module can exist separately, or two or more modules can be integrated to form an independent part. If the function is implemented in the form of a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a disk or an optical disk.

[0248] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0249] The above are only various implementations of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A distributed file upload verification method, It is characterized in that The distributed file upload verification method comprises the following steps: Obtain a file to be uploaded, split the file to be uploaded into multiple data blocks according to a preset threshold, upload the multiple data blocks to a distributed file system, obtain upload information of each data block through the distributed file system, and store the upload information of each data block in an Uploading linked list; Integrate the upload information in the Uploading linked list to obtain integrated data, wherein the integrated data includes the upload information of each data block, and upload the integrated data to the Upload-Result linked list; monitoring the integrated data of the Upload-Result linked list in real time, and when detecting the existence of a successfully uploaded data block, comparing the successfully uploaded data block through the distributed file system; If the successfully uploaded data block has an abnormality, the user is prompted that the upload is abnormal; if all of the multiple data blocks have no abnormalities, the user is prompted that the upload is successful.

2. The distributed file upload verification method according to claim 1, It is characterized in that After the step of if the successfully uploaded data block has an abnormality, the method further includes: The abnormal data blocks are deleted from the distributed file system.

3. The distributed file upload verification method according to claim 1, It is characterized in that After the step of real-time monitoring the integrated data of the Upload-Result linked list, the method further includes: When it is detected that there is a data block that fails to be uploaded, the data block that fails to be uploaded is marked and the data block that fails to be uploaded is deleted from the distributed file system.

4. The distributed file upload verification method according to claim 1, It is characterized in that If the successfully uploaded data block has an abnormality, prompt the user to upload the abnormality; If there are no abnormalities in the plurality of data blocks, after prompting the user that the upload is successful, the method further includes: Integrate all successfully uploaded data block information into the Monitor-Result linked list. When the user re-uploads the file to be uploaded, determine the data blocks to be uploaded that need to be re-uploaded according to the Monitor-Result linked list, and upload the data blocks to be uploaded to the distributed file system; If the data block to be uploaded is uploaded successfully, the user is prompted that the upload is successful.

5. The distributed file upload verification method according to claim 4, It is characterized in that After the step of integrating all successfully uploaded data block information into the Monitor-Result linked list, the following steps are also included: The upload information corresponding to all successfully uploaded data block information is deleted from the Upload-Result linked list.

6. The distributed file upload verification method according to claim 4, It is characterized in that After the step of successfully uploading the data block to be uploaded, the method further includes: All successfully uploaded data block information in the Monitor-Result linked list is persistently stored in the database. If the persistent storage is successful, the persistently stored data block information in the Monitor-Result linked list is deleted.

7. The distributed file upload verification method according to claim 1, It is characterized in that The step of uploading the plurality of data blocks to the distributed file system comprises: The multiple data blocks are uploaded to the distributed file system in a multi-threaded uploading manner.

8. A distributed file upload verification device, It is characterized in that The distributed file upload verification device comprises: A file splitting and uploading module, which obtains a file to be uploaded, splits the file to be uploaded into multiple data blocks according to a preset threshold, uploads the multiple data blocks to a distributed file system, obtains upload information of each data block through the distributed file system, and stores the upload information of each data block in an Uploading linked list; An upload information integration module integrates the upload information in the Uploading linked list to obtain integrated data, wherein the integrated data includes the upload information of each data block, and uploads the integrated data to the Upload-Result linked list; An upload status monitoring module monitors the integrated data of the Upload-Result linked list in real time, and when a successfully uploaded data block is detected, compares the successfully uploaded data block through the distributed file system; The verification result prompt module prompts the user that the upload is abnormal if there is an abnormality in the successfully uploaded data block; if there is no abnormality in all the multiple data blocks, prompts the user that the upload is successful.

9. A distributed file upload verification device, It is characterized in that The distributed file upload verification device includes a memory, a processor, and a distributed file upload verification program stored in the memory and executable on the processor. When the distributed file upload verification program is executed by the processor, the steps of the distributed file upload verification method according to any one of claims 1 to 7 are implemented.

10. A computer storage medium, It is characterized in that The storage medium stores a distributed file upload verification program, which, when executed by the processor, implements the steps of the distributed file upload verification method according to any one of claims 1 to 7.

Citation Information

Patent Citations

  • File uploading method and system based on distributed file storage system

    CN107508897A

  • Monitoring method, system, device and medium for distributed file storage cluster

    CN109522287A

  • File processing method and device, computer readable storage medium and server

    CN114398332A

  • Large file fragment concurrent uploading method based on WebUploader

    CN118316923A