A file deployment method and device, a server and a computer readable storage medium

Abstract

The application discloses a file deployment method, relates to the technical field of file management, and comprises the following steps: counting the number of times of request non-return points; the number of times of request non-return points is the number of times of not returning node information to a client; the node information comprises information of a node capable of providing a target file for the client; obtaining the deployment quantity of the target file according to the number of times of request non-return points and a preset deployment rule; and deploying the target file to each target node according to the deployment quantity. The method can timely and accurately deploy files. The application further discloses a file deployment device, a server and a computer readable storage medium, which all have the technical effects.

Description

Technical Field

[0001] This application relates to the field of document management technology, and in particular to a document deployment method; it also relates to a document deployment device, a server, and a computer-readable storage medium. Background Technology

[0002] In applications such as CDN (Content Delivery Network) systems and video-on-demand services, files are deployed on node devices such as cloud servers, x86 devices, personal computers, and smart routers, and users retrieve files from these node devices. Currently, the file deployment strategy calculates a file popularity value based on user requests, then assesses deployment needs based on this value and deploys the file to the node devices. However, deploying files based solely on popularity values ​​can lead to inaccurate and untimely deployments. Therefore, providing a technical solution that enables timely and accurate file deployment has become a pressing technical problem for those skilled in the art. Summary of the Invention

[0003] The purpose of this application is to provide a file deployment method that enables timely and accurate file deployment. Another purpose of this application is to provide a file deployment apparatus, server, and computer-readable storage medium, all of which have the aforementioned technical effects.

[0004] To address the aforementioned technical problems, this application provides a file deployment method, comprising:

[0005] The number of requests that do not return a node information is counted; the number of requests that do not return a node information is the number of times node information is not returned to the client; the node information includes information about nodes that can provide the target file to the client.

[0006] Based on the number of requests without return and the preset deployment rules, the number of deployment copies of the target file is obtained;

[0007] The target file is deployed to each target node according to the number of deployment copies.

[0008] Optionally, determining the number of deployment copies of the target file based on the number of requests without penalty and preset deployment rules includes:

[0009] Based on the number of requests without return points and the preset deployment rules, the number of deployment copies of the target file in each round is obtained;

[0010] Accordingly, deploying the target file to each target node according to the number of deployment copies includes:

[0011] Based on the number of deployment copies of the target file in each round, the target file is deployed to each target node in rounds.

[0012] Optionally, the number of times the statistics request does not return points includes:

[0013] The number of requests that do not return are counted according to a preset period, so that after each count of the number of requests that do not return are counted, the number of deployment copies of the target file in each round can be obtained based on the count of the number of requests that do not return in this count and the preset deployment rules.

[0014] Optionally, the rule parameters in the preset deployment rules include:

[0015] File deployment speed, maximum number of files deployed, minimum number of files deployed, and / or the number of files deployed in a single instance; the file deployment speed refers to the number of files deployed in this instance.

[0016] Optionally, the step of determining the number of deployment copies of the target file in each round based on the number of requests without return and the preset deployment rules includes:

[0017] Based on the number of requests without refunds and the rule parameters, the expected number of deployments is obtained;

[0018] Compare the desired number of deployments with the number of single file deployments;

[0019] If the expected number of deployments is less than the number of single file deployments, then the expected number of deployments will be used as the number of deployments of the target file in each round.

[0020] If the expected number of deployments is greater than or equal to the number of single file deployments, then the number of single file deployments is taken as the number of deployments of the target file in each round.

[0021] Optionally, obtaining the desired number of deployments based on the number of requests without return and the rule parameters includes:

[0022] Based on the range of non-return requests that the number of non-return requests falls within, determine the corresponding values ​​for the file deployment speed, the maximum number of files to be deployed, the minimum number of files to be deployed, and the number of files to be deployed in a single instance.

[0023] When the sum of the number of deployed copies of a file and the number of copies of a file being deployed is less than or equal to the maximum number of copies of the file to be deployed, determine whether the sum of the number of deployed copies of the file and the number of copies of the file being deployed is less than the minimum number of copies of the file to be deployed;

[0024] If so, the maximum value between the file deployment speed and the deployment gap value is taken as the expected number of deployments; wherein, the deployment gap value is the difference between the minimum number of file deployments minus the number of file already deployed and the number of file currently being deployed;

[0025] If not, the difference between the file deployment speed and the number of copies of the file being deployed is taken as the expected number of copies to be deployed.

[0026] Optionally, the node information includes information about nodes within the partition to which the client belongs that can provide the target file to the client.

[0027] Optionally, the number of requests that do not return are the number of times node information is not returned to the client within a preset time. When the same client sends multiple requests to obtain the same target file within the preset time, and none of them return node information that can provide the target file to the client, the number of requests that do not return are counted as one.

[0028] To address the aforementioned technical problems, this application also provides a file deployment apparatus, comprising:

[0029] The statistics module is used to count the number of requests that do not return a node; the number of requests that do not return a node is the number of times node information is not returned to the client; the node information includes information about nodes that can provide the target file to the client;

[0030] The analysis module is used to determine the number of deployment copies of the target file based on the number of times the request does not return and the preset deployment rules.

[0031] The deployment module is used to deploy the target file to each target node according to the number of deployment copies.

[0032] To address the aforementioned technical problems, this application also provides a server, comprising:

[0033] Memory, used to store computer programs;

[0034] A processor for executing the computer program to implement the steps of the file deployment method as described above.

[0035] To address the aforementioned technical problems, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the file deployment method described above.

[0036] The file deployment method provided in this application includes: counting the number of requests that do not return a response; the number of requests that do not return a response is the number of times node information is not returned to the client; the node information includes information about nodes that can provide the target file to the client; obtaining the number of deployment copies of the target file according to the number of requests that do not return a response and a preset deployment rule; and deploying the target file to each target node according to the number of deployment copies.

[0037] As can be seen, the file deployment method provided in this application deploys files based on the number of times a request is not returned. This number reflects the number of times a client's request has not been responded to. Deploying files based on this number allows for client-driven file deployment. Regardless of the reason why a client's request was not responded to, as long as there is a number of times a request is not returned, files can be deployed based on this number, achieving accurate and timely file deployment. Furthermore, the file deployment method provided in this application does not involve a complex evaluation between popularity value and the number of deployments, making it easier to implement.

[0038] The file deployment device, server, and computer-readable storage medium provided in this application all have the aforementioned technical effects. Attached Figure Description

[0039] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the prior art and embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0040] Figure 1 A flowchart illustrating a file deployment method provided in an embodiment of this application;

[0041] Figure 2 A file deployment framework provided in the embodiments of this application;

[0042] Figure 3 A schematic diagram illustrating a process for calculating the number of deployment copies provided in an embodiment of this application;

[0043] Figure 4 A schematic diagram illustrating a process for calculating the desired number of deployments, provided as an embodiment of this application;

[0044] Figure 5 This is a schematic diagram of a file deployment device provided in an embodiment of this application;

[0045] Figure 6 This is a schematic diagram of a server provided in an embodiment of this application. Detailed Implementation

[0046] The core of this application is to provide a file deployment method that enables timely and accurate file deployment. Another core aspect of this application is to provide a file deployment device, server, and computer-readable storage medium, all of which achieve the aforementioned technical effects.

[0047] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0048] Please refer to Figure 1 , Figure 1 This is a flowchart illustrating a file deployment method provided in an embodiment of this application. (Refer to...) Figure 1 As shown, the method includes:

[0049] S101: Count the number of requests that do not return node information; the number of requests that do not return node information refers to the number of times node information is not returned to the client; the node information includes information about nodes that can provide the target file to the client.

[0050] refer to Figure 2 As shown, when a client wants to obtain a file, it sends a scheduling request to the scheduling system. This request aims to retrieve information about nodes that can provide the required file, allowing the client to obtain the file from the appropriate node. Node information may include the node's IP address, node ID, etc. If a node can provide the target file, the scheduling system returns this information to the client. Otherwise, it does not.

[0051] The scheduling system can return node information to the client in the form of a node list. This node list includes information about one or more nodes that can provide the target file to the client.

[0052] The deployment system is responsible for counting the number of requests that were not returned. It should be noted that the number of requests that were not returned is the sum of the number of requests for the same file made by all clients.

[0053] For example, client 1's target file is file 1, client 2's target file is file 1, and client 3's target file is file 2. If the scheduling system does not return a target file to clients 1, 2, or 3, since client 1 and client 2's target file is file 1, the number of times requests for file 1 are not returned is 2, while the number of times requests for file 2 are not returned is 1.

[0054] In addition, in some embodiments, the number of requests that do not return a node is the number of times node information is not returned to the client within a preset time. When the same client sends multiple requests to obtain the same target file within the preset time, and none of them return node information that can provide the target file to the client, the number of requests that do not return a node is counted as one.

[0055] The preset time can be 30 minutes, one hour, etc. Regardless of whether the same client sends one request or multiple requests to the scheduling system for the same file within the preset time, if the scheduling system does not return information about a node that can provide the file to the client within the preset time, the client's request for the file without a return is counted as one. This allows for a more reasonable count of requests without a return and more accurate file deployment.

[0056] For example, client 1's target file is file 1. Within a preset time period, client 1 sends multiple requests to the scheduling system, but the scheduling system does not return any information about a node that can provide file 1. For file 1, the number of times client 1's requests fail to return a node within the preset time period is 1. Client 2's target file is file 1. Within the preset time period, client 2 sends one request to the scheduling system, but the scheduling system does not return any information about a node that can provide file 1. For file 1, the number of times client 2's requests fail to return a node within the preset time period is also 1. Therefore, the total number of times requests for file 1 fail to return a node is the sum of client 1's and client 2's, which equals 2.

[0057] If any node deploys the target file, the number of nodes providing file download services can be determined based on the number of client requests and node information (including the number of nodes deploying the target file and whether the nodes can provide file download services). Check if the number of nodes providing file download services is greater than the number of client requests; if so, there's no need to count the number of requests that didn't return a request. If not, then count the number of requests that didn't return a request; if no node deploys the target file, then the number of requests that didn't return a request can be counted directly.

[0058] Furthermore, the statistical range for the number of requests without return requests is consistent with the deployment range of the target file. That is, after counting the number of requests without return requests within a certain range and calculating the number of deployment copies of the target file, the target file is deployed to the target nodes within that range based on that number of deployment copies. The scope of statistics and deployment can be divided by partitioning the client and nodes. The deployment system counts the number of requests without return requests within the same partition and deploys the target file to the target nodes within that partition. Alternatively, other methods can be used to divide the scope of statistics and deployment.

[0059] In some embodiments, the node information includes information about nodes within the partition to which the client belongs that can provide the target file to the client.

[0060] In this embodiment, the client and nodes are partitioned. The scheduling system returns information about the nodes within the client's partition that can provide the target file to the client. If the scheduling system does not return information about nodes within its partition that can provide the target file to the client, it is considered a non-return request for that target file.

[0061] If the scheduling system does not return information about nodes within its own partition that can provide the target file to the client, that is, if the client cannot obtain the target file from nodes within its own partition, the scheduling system can still return information about nodes in the nearest other partition that can provide the target file to the client if nodes in other partitions can provide the target file to the client, so that the client can obtain the target file across partitions.

[0062] Clients and nodes can be partitioned based on geographical location. For example, certain geographical locations can be used as boundaries to divide the region into five partitions: North, Central, South, West, and East. Partitioning can also be based on administrative regions, such as using each provincial-level administrative region as a partition. Other more granular partitioning methods are also possible.

[0063] S102: Based on the number of requests without return and the preset deployment rules, obtain the number of deployment copies of the target file;

[0064] S103: Deploy the target file to each target node according to the number of deployment copies.

[0065] Based on the count of requests for non-return requests, the deployment system further calculates the number of deployment copies of the target file according to the number of non-return requests and preset deployment rules, and deploys the target file to the target nodes according to the number of deployment copies. Target nodes refer to the nodes selected for deploying the target file. The number of target nodes can be equal to the number of deployment copies, or they can be different. For example, if the selected nodes for deploying the target file are nodes with strong stability and service capabilities, then the number of target nodes can be less than the number of deployment copies.

[0066] In some embodiments, the number of deployment copies of the target file is obtained based on the number of requests without penalty and a preset deployment rule, including:

[0067] Based on the number of requests without return points and the preset deployment rules, the number of deployment copies of the target file in each round is obtained;

[0068] Accordingly, deploying the target file to each target node according to the number of deployment copies includes:

[0069] Based on the number of deployment copies of the target file in each round, the target file is deployed to each target node in rounds.

[0070] This embodiment determines the number of deployments per round based on the number of requests for non-return points and preset deployment rules, and then deploys the target files to each target node in each round.

[0071] For example, based on the number of requests without penalty and the preset deployment rules, the number of deployments in the first round is 3, and the first round of file deployment is performed accordingly. Further based on the number of requests without penalty and the preset deployment rules, the number of deployments in the second round is 2, and the second round of file deployment is performed accordingly.

[0072] In some embodiments, the number of times a request is not refunded includes:

[0073] The number of requests that do not return are counted according to a preset period, so that after each count of the number of requests that do not return are counted, the number of deployment copies of the target file in each round can be obtained based on the count of the number of requests that do not return in this count and the preset deployment rules.

[0074] This embodiment periodically counts the number of requests that do not return to the previous period. After each count, based on the current count and preset deployment rules, the number of deployment copies of the target file for each round is calculated, and the target file is deployed round by round. In this case, the period for counting the number of requests that do not return to the previous period is the same as the period for calculating the number of deployment copies. Alternatively, the period for counting the number of requests that do not return to the previous period and the period for calculating the number of deployment copies can be different. For example, the operation of counting the number of requests that do not return to the previous period can be performed periodically, while the operation of calculating the number of deployment copies of the target file can be performed only once after multiple counts of requests that do not return to the previous period have been completed. Another example is that after one count of requests that do not return to the previous period is completed, multiple operations to calculate the number of deployment copies are performed.

[0075] A preset deployment rule refers to a pre-defined rule used to calculate the number of deployments, including rule parameters. Rule parameters are the parameters used to calculate the number of deployments, and the value of these parameters can be customized. In some embodiments, the rule parameters in the preset deployment rule include:

[0076] File deployment speed, maximum number of files deployed, minimum number of files deployed, and / or the number of files deployed in a single instance; the file deployment speed refers to the number of files deployed in this instance.

[0077] Based on the above embodiments, as a specific implementation method, obtaining the number of deployment copies of the target file in each round according to the number of requests without return points and the preset deployment rules includes:

[0078] Based on the number of non - rebate requests and the rule parameters, obtain the expected deployment quantity.

[0079] Compare the expected deployment quantity with the single - file deployment quantity.

[0080] If the expected deployment quantity is less than the single - file deployment quantity, then use the expected deployment quantity as the deployment quantity of the target file for each round.

[0081] If the expected deployment quantity is greater than or equal to the single - file deployment quantity, then use the single - file deployment quantity as the deployment quantity of the target file for each round.

[0082] Reference Figure 3 As shown, the expected deployment quantity is denoted as expect, the single - file deployment quantity is denoted as copyonce, and the deployment quantity of the target file for each round is denoted as plan. If expect < copyonce, then plan = expect. If expect ≥ copyonce, then plan = copyonce.

[0083] Among them, as shown in the reference Figure 4 In some embodiments, the obtaining of the expected deployment quantity according to the number of non - rebate requests and the rule parameters includes:

[0084] According to the range of the number of non - rebate requests of the request, determine the corresponding values of the file deployment speed, the maximum file deployment quantity, the minimum file deployment quantity, and the single - file deployment quantity.

[0085] When the sum of the deployed file quantity and the file being deployed quantity is less than or equal to the maximum file deployment quantity, determine whether the sum of the deployed file quantity and the file being deployed quantity is less than the minimum file deployment quantity.

[0086] If so, then use the maximum value between the file deployment speed and the deployment vacancy value as the expected deployment quantity; where the deployment vacancy value is the difference obtained by subtracting the deployed file quantity and the file being deployed quantity from the minimum file deployment quantity.

[0087] If not, then use the difference between the file deployment speed and the file being deployed quantity as the expected deployment quantity.

[0088] The values ​​of the rule parameters can differ depending on the range of the number of requests that do not incur a penalty. For example, if the number of requests that do not incur a penalty is 1 to 3, the corresponding values ​​for file deployment speed, maximum number of files deployed, minimum number of files deployed, and number of files deployed in a single instance are 4, 100, 2, and 2, respectively. If the number of requests that do not incur a penalty is 3 to 5, the corresponding values ​​for file deployment speed, maximum number of files deployed, minimum number of files deployed, and number of files deployed in a single instance are 4, 100, 6, and 6, respectively.

[0089] The number of deployed copies of a file is denoted as `index`, the number of copies currently being deployed is denoted as `planed`, the minimum number of copies to be deployed is denoted as `copymin`, the maximum number of copies to be deployed is denoted as `copymax`, and the deployment speed is denoted as `copyrate`. If `index + planed` ≤ `copymax`, then it is checked whether `index + planed` is less than `copymin`. If `index + planed` < `copymin`, then `except` = `max(copyrate, copymin - index - planed)`. If `index + planed` ≥ `copymin`, then `except` = `copyrate`. If `index + planed` > `copymax`, then `except` = `copyrate`, and the number of deployed copies is not further calculated. Furthermore, if `except` ≤ 0, the number of deployed copies is not further calculated.

[0090] In summary, the file deployment method provided in this application deploys files based on the number of times a request was not returned, which reflects the number of times a client's request was not answered. Deploying files based on the number of times a request was not returned allows for file deployment driven by client needs. Regardless of the reason why a client's request was not answered, as long as there is a number of times a request was not returned, files can be deployed based on this number, achieving accurate and timely file deployment. Furthermore, the file deployment method provided in this application does not involve a complex evaluation between popularity value and the number of deployments, making it easier to implement.

[0091] This application also provides a file deployment apparatus, which is described below and can be referred to in conjunction with the method described above. Please refer to... Figure 5 , Figure 5 This is a schematic diagram of a file deployment device provided in an embodiment of this application, combined with... Figure 5 As shown, the device includes:

[0092] The statistics module 10 is used to count the number of requests that do not return a node; the number of requests that do not return a node is the number of times node information is not returned to the client; the node information includes information about nodes that can provide the target file to the client;

[0093] Analysis module 20 is used to obtain the number of deployment copies of the target file based on the number of requests that do not return points and preset deployment rules;

[0094] The deployment module 30 is used to deploy the target file to each target node according to the number of deployment copies.

[0095] Based on the above embodiments, as a specific implementation method, the analysis module 20 is specifically used for:

[0096] Based on the number of requests without return points and the preset deployment rules, the number of deployment copies of the target file in each round is obtained;

[0097] Accordingly, deployment module 30 is specifically used for:

[0098] Based on the number of deployment copies of the target file in each round, the target file is deployed to each target node in rounds.

[0099] Based on the above embodiments, as a specific implementation method, the statistics module 10 is specifically used for:

[0100] The number of requests that do not return are counted according to a preset period, so that after each count of the number of requests that do not return are counted, the number of deployment copies of the target file in each round can be obtained based on the count of the number of requests that do not return in this count and the preset deployment rules.

[0101] Based on the above embodiments, as a specific implementation method, the rule parameters in the preset deployment rules include:

[0102] File deployment speed, maximum number of files deployed, minimum number of files deployed, and / or the number of files deployed in a single instance; the file deployment speed refers to the number of files deployed in this instance.

[0103] Based on the above embodiments, as a specific implementation method, the analysis module 20 includes:

[0104] The calculation unit is used to obtain the expected number of deployments based on the number of requests that do not return points and the rule parameters;

[0105] The comparison unit is used to compare the expected number of deployments with the number of single file deployments;

[0106] The first determining unit is configured to, if the expected number of deployment copies is less than the number of single file deployment copies, use the expected number of deployment copies as the number of deployment copies of the target file in each round;

[0107] The second determining unit is configured to, if the expected number of deployments is greater than or equal to the number of single file deployments, use the number of single file deployments as the number of deployments of the target file in each round.

[0108] Based on the above embodiments, as a specific implementation method, the computing unit includes:

[0109] The numerical determination subunit is used to determine the corresponding values ​​of the file deployment speed, the maximum number of files to be deployed, the minimum number of files to be deployed, and the number of files to be deployed in a single instance, based on the range of the number of requests that do not return to the request.

[0110] The judgment subunit is used to determine whether the sum of the number of deployed copies of a file and the number of copies of a file being deployed is less than the minimum number of copies of a file when the sum of the number of deployed copies of a file and the number of copies of a file being deployed is less than or equal to the maximum number of copies of a file to be deployed.

[0111] The first determining subunit is configured to, if so, take the maximum value between the file deployment speed and the deployment gap value as the expected number of deployments; wherein, the deployment gap value is the difference between the minimum number of file deployments minus the number of file already deployed and the number of file currently being deployed;

[0112] The second determining subunit is used to, if not, subtract the number of copies of the file being deployed from the file deployment speed as the expected number of copies to be deployed.

[0113] Based on the above embodiments, as a specific implementation method, the node information includes information about nodes within the partition to which the client belongs that can provide the target file to the client.

[0114] Based on the above embodiments, as a specific implementation method, the number of requests without return points is the number of times node information is not returned to the client within a preset time. When the same client sends multiple requests to obtain the same target file within the preset time, and none of them return node information that can provide the target file to the client, the number of requests without return points for the client is counted as one.

[0115] The file deployment device provided in this application deploys files based on the number of times a request was not returned, which reflects the number of times a client's request was not answered. Deploying files based on the number of times a request was not returned allows file deployment to be driven by client needs. Regardless of the reason why a client's request was not answered, as long as there is a number of times a request was not returned, the file can be deployed based on this number, achieving accurate and timely file deployment. Furthermore, the file deployment device provided in this application does not involve a complex evaluation between popularity value and the number of deployments, making it easier to implement.

[0116] This application also provides a server, for reference Figure 6As shown, the device includes a memory 1 and a processor 2.

[0117] Memory 1 is used to store computer programs;

[0118] Processor 2 is used to execute computer programs to perform the following steps:

[0119] The number of requests that do not return a node information is counted; the number of requests that do not return a node information is the number of times node information is not returned to the client; the node information includes information about nodes that can provide the target file to the client.

[0120] Based on the number of requests without return and the preset deployment rules, the number of deployment copies of the target file is obtained;

[0121] The target file is deployed to each target node according to the number of deployment copies.

[0122] For a description of the server provided in this application, please refer to the above method embodiments; further details will not be provided here.

[0123] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can perform the following steps:

[0124] The number of requests that do not return a node information is counted; the number of requests that do not return a node information is the number of times node information is not returned to the client; the node information includes information about nodes that can provide the target file to the client.

[0125] Based on the number of requests without return and the preset deployment rules, the number of deployment copies of the target file is obtained;

[0126] The target file is deployed to each target node according to the number of deployment copies.

[0127] The computer-readable storage medium may include various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0128] For a description of the computer-readable storage medium provided in this application, please refer to the above method embodiments; further details will not be repeated here.

[0129] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus, server, and computer-readable storage medium disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple; relevant details can be found in the method section.

[0130] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0131] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0132] The document deployment method, apparatus, server, and computer-readable storage medium provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are merely for the purpose of helping to understand the method and core ideas of this application. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A file deployment method, characterized in that, include: Count the number of requests that do not receive a refund; The number of times a request is not returned refers to the number of times node information is not returned to the client. The node information includes information about nodes that can provide the target file to the client; The number of requests that do not return a reward is the sum of the number of requests that do not return a reward from each client for the same file; The value of the rule parameter in the preset deployment rule is determined based on the number of times the request does not return points, and the expected number of deployments is determined based on the value of the rule parameter. Compare the desired number of deployments with the number of single file deployments in the rule parameters; If the expected number of deployments is less than the number of single file deployments, then the expected number of deployments will be used as the number of deployments of the target file in each round. If the expected number of deployments is greater than or equal to the number of single file deployments, then the number of single file deployments is taken as the number of deployments of the target file in each round. The target file is deployed to each target node according to the number of deployment copies.

2. The file deployment method according to claim 1, characterized in that, The step of deploying the target file to each target node according to the number of deployment copies includes: Based on the number of deployment copies of the target file in each round, the target file is deployed to each target node in rounds.

3. The file deployment method according to claim 2, characterized in that, The number of times the statistical request did not return a reward includes: The number of requests that do not return are counted according to a preset period, so that after each count of the number of requests that do not return are counted, the number of deployment copies of the target file in each round can be obtained based on the count of the number of requests that do not return in this count and the preset deployment rules.

4. The file deployment method according to claim 2, characterized in that, The rule parameters in the preset deployment rules include: File deployment speed, maximum number of files deployed, minimum number of files deployed, and / or the number of files deployed in a single instance; the file deployment speed refers to the number of files deployed in this instance.

5. The file deployment method according to claim 4, characterized in that, The step of determining the value of the rule parameter in the preset deployment rule based on the number of requests without return points, and determining the expected number of deployments based on the value of the rule parameter, includes: Based on the range of non-return requests that the number of non-return requests falls within, determine the corresponding values ​​for the file deployment speed, the maximum number of files to be deployed, the minimum number of files to be deployed, and the number of files to be deployed in a single instance. When the sum of the number of deployed copies of a file and the number of copies of a file being deployed is less than or equal to the maximum number of copies of the file to be deployed, determine whether the sum of the number of deployed copies of the file and the number of copies of the file being deployed is less than the minimum number of copies of the file to be deployed; If so, the maximum value between the file deployment speed and the deployment gap value is taken as the expected number of deployments; wherein, the deployment gap value is the difference between the minimum number of file deployments minus the number of file already deployed and the number of file currently being deployed; If not, the difference between the file deployment speed and the number of copies of the file being deployed is taken as the expected number of copies to be deployed.

6. The file deployment method according to claim 1, characterized in that, The node information includes information about nodes within the partition to which the client belongs that can provide the target file to the client.

7. The file deployment method according to claim 1, characterized in that, The number of requests that do not return a node is the number of times node information is not returned to the client within a preset time. If the same client sends multiple requests to obtain the same target file within the preset time, and none of them return node information that can provide the target file to the client, the number of requests that do not return a node is counted as one.

8. A file deployment device, characterized in that, include: The statistics module is used to count the number of requests that do not return points. The number of times a request is not returned refers to the number of times node information is not returned to the client. The node information includes information about nodes that can provide the target file to the client; The number of requests that do not return a reward is the sum of the number of requests that do not return a reward from each client for the same file; The analysis module is used to determine the value of the rule parameter in the preset deployment rule based on the number of times the request does not return, and to determine the expected number of deployments based on the value of the rule parameter. Compare the expected number of deployments with the single file deployment number in the rule parameters; if the expected number of deployments is less than the single file deployment number, then the expected number of deployments is used as the number of deployments of the target file in each round; if the expected number of deployments is greater than or equal to the single file deployment number, then the single file deployment number is used as the number of deployments of the target file in each round. The deployment module is used to deploy the target file to each target node according to the number of deployment copies.

9. A server, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the steps of the file deployment method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the file deployment method as described in any one of claims 1 to 7.

Images