Service request processing method and device and computer equipment

Abstract

The invention relates to a service request processing method and apparatus, and a computer device. The method comprises the steps of obtaining a target service access request for a target object in a distributed storage system; determining a demand flow token of a flow limiting index corresponding to the target object when the target object is accessed; and according to the demand traffic token and the local residual traffic token, determining whether to perform traffic limiting processing on the target service access request. According to the scheme, the QoS client can determine whether the target service request needs to be subjected to flow limiting or not according to the demand flow token and the local residual flow token, interaction with the QoS management end is not needed, extra consumption of network resources caused by the fact that the QoS client inquires the flow limiting query message from the QoS management end is avoided, and user experience is improved. Therefore, the performance of the distributed storage system is ensured while the service processing request is subjected to flow limiting.

Description

Technical Field

[0001] The present application relates to the field of distributed storage technology, and in particular to a method, apparatus and computer device for processing business requests. Background Art

[0002] Distributed storage systems connect multiple storage devices through the network to form a unified, scalable storage resource pool, providing data storage and access services to the outside world. When the business request traffic far exceeds the system's load capacity, if there is no flow control, the system may crash due to overload, resulting in service unavailability. In order to ensure that the distributed storage system runs stably in a high-concurrency, high-load environment, it is usually necessary to limit the flow of business requests.

[0003] In traditional technology, after a service request reaches a client, it first interacts with a Quality of Service Manager (QoS MGR) to check whether the current service request is limited.

[0004] However, when the scale of the distributed storage system is relatively large, such as when the number of storage nodes reaches tens of thousands, as the business pressure increases, the amount of flow-limited query messages between the client and the QoS MGR is very large, and the additional consumption of message processing and network resources will seriously affect normal business performance. Summary of the invention

[0005] Based on this, it is necessary to provide a business request processing method, device and computer equipment to address the above technical problems, which can limit the flow of business processing requests and ensure the performance of the distributed storage system.

[0006] In a first aspect, the present application provides a service request processing method, the method being applied to a quality of service QoS client, the method comprising:

[0007] Obtain a target business access request for a target object in a distributed storage system;

[0008] Determine a demand flow token for a flow limiting indicator corresponding to the target object when accessing the target object; wherein the flow limiting indicator corresponding to the target object includes bandwidth and / or IOPS;

[0009] Determine whether to perform flow limiting processing on the target service access request based on the demand flow token and the local remaining flow token of the flow limiting indicator corresponding to the target object; wherein the local remaining flow token is the remaining flow token in the flow token of the flow limiting indicator of the target object allocated by the QoS management end to the QoS client.

[0010] In the embodiment of the present application, since the local remaining flow token is the remaining flow token in the flow token of the flow limiting indicator for the target object allocated by the QoS management end to the QoS client, when determining whether it is necessary to limit the flow of the target service request, the QoS client can determine it based on the required flow token and the local remaining flow token without interacting with the QoS management end, thereby avoiding the additional consumption of network resources caused by the QoS client asking the QoS management end for the flow limiting query message, and then ensuring the performance of the distributed storage system while being able to limit the flow of service processing requests.

[0011] In one of the embodiments, when the flow limiting indicator includes bandwidth and IOPS, determining whether to perform flow limiting processing on the target service access request according to the demand flow token and the local remaining flow token of the flow limiting indicator corresponding to the target object includes:

[0012] Compare the demand flow token corresponding to each flow limiting indicator with the local remaining flow token;

[0013] If there is any flow-limiting indicator corresponding to a demand flow token that is greater than the local remaining flow token, it is determined that the target service access request needs to be flow-limited.

[0014] In an embodiment of the present application, by comparing whether the demand flow token corresponding to each flow limiting indicator of the target object is greater than the local remaining flow token, if there is any flow limiting indicator corresponding to a demand flow token greater than the local remaining flow token, it is determined that the target business access request needs to be flow limited, thereby avoiding the problem of access to the target object being blocked when the access flow of a certain flow limiting indicator of the target object is greater than the flow target.

[0015] In one embodiment, the target service access request is subjected to flow limiting processing, including:

[0016] The target service access request is added to a waiting queue.

[0017] In the embodiment of the present application, by adding the target service access request to the waiting queue, the target service access request is subjected to flow limiting processing, thereby avoiding the problem of access congestion caused by the flow of accessing the target object exceeding the target flow.

[0018] In one embodiment, after adding the target service access request to the waiting queue, the method further includes:

[0019] If a new flow token for the flow limiting indicator of the target object is received from the QoS management terminal, and / or a flow token release event for the flow limiting indicator corresponding to the target object is detected by other service access requests, the local remaining flow token of the flow limiting indicator corresponding to the target object is updated;

[0020] When the updated local remaining traffic token is greater than or equal to the demand traffic token, extracting the target service access request from the waiting queue;

[0021] The demand flow token is allocated to the target service access request, and the target object is accessed based on the allocated demand flow token.

[0022] In an embodiment of the present application, when the local remaining traffic token is updated, it continues to be determined whether the local remaining traffic token can satisfy the target business access request to access the target object, thereby minimizing the waiting time for the target business access request to be processed and speeding up the efficiency of processing the target business access request.

[0023] In one of the embodiments, the local remaining traffic token is the remaining traffic token in the traffic token of the flow limiting indicator for the target object allocated by the QoS management end to the QoS client in the current service reporting period;

[0024] Before obtaining the target service access request for the target object in the distributed storage system, the method further includes:

[0025] Determine the service information of the current service reporting cycle according to the total flow token of the flow limiting indicator corresponding to the access restriction object of each service access request received by the QoS client in the previous service reporting cycle; the access restriction object is an object in the distributed storage system that needs to be subject to flow access restriction, and the access restriction object at least includes the target object;

[0026] Reporting the service information to the QoS management end, so that the QoS management end determines the token information corresponding to each QoS client in the current service reporting period based on the service information reported by each QoS client;

[0027] Receive the corresponding token information sent by the QoS management end; wherein the token information includes the flow token of the flow limiting indicator corresponding to the access restriction object.

[0028] In an embodiment of the present application, the QoS management end reports service information to the QoS client in each service reporting cycle, so that the QoS management end determines to send corresponding token information to the QoS client based on the service information, which can make more effective use of traffic tokens and improve the processing efficiency of service access requests.

[0029] In a second aspect, the present application also provides a service request processing method, which is applied to a QoS service end, and the method includes:

[0030] Send corresponding token information to each QoS client, so that each QoS client determines whether to perform flow limiting processing on the received service access request based on the corresponding token information and the demand flow token of the flow limiting indicator corresponding to the object targeted by the received service access request;

[0031] Among them, the token information corresponding to each QoS client includes the flow token of the flow limiting indicator corresponding to the access restriction object associated with the QoS client; the access restriction object is an object in the distributed storage system that requires flow access restriction.

[0032] In an embodiment of the present application, the QoS server sends a traffic token to the QoS client. When determining whether it is necessary to limit the flow of service access requests, it only needs the QoS client's required traffic token and the local remaining traffic token to determine it, without the need to interact with the QoS management end. This avoids the additional consumption of network resources caused by the QoS client asking the QoS management end for flow limiting query messages, thereby ensuring the performance of the distributed storage system while being able to limit the flow of service processing requests.

[0033] In one embodiment, the sending corresponding token information to each QoS client includes:

[0034] Receive service information reported by each QoS client in the current service reporting cycle; wherein the service information reported by each QoS client is determined according to the total flow token of the flow limiting indicator corresponding to the access restriction object of each service access request received by the QoS client in the previous service reporting cycle;

[0035] Determine, according to the service information reported by each QoS client, the token information corresponding to each QoS client in the current service reporting period;

[0036] Send the corresponding token information to each QoS client.

[0037] In an embodiment of the present application, based on the service information reported by each QoS client in the current service reporting period, the corresponding token information is determined to be sent to each QoS client, so that the traffic token can be more fully utilized and the processing efficiency of service access requests can be improved.

[0038] In a third aspect, the present application further provides a service request processing device, the device being configured in a QoS client, the device comprising:

[0039] An acquisition module, used to acquire a target service access request for a target object in a distributed storage system;

[0040] A first determination module is used to determine a demand flow token for a flow limiting indicator corresponding to the target object when accessing the target object; wherein the flow limiting indicator corresponding to the target object includes bandwidth and / or IOPS;

[0041] The second determination module is used to determine whether to perform flow limiting processing on the target service access request based on the demand flow token and the local remaining flow token of the flow limiting indicator corresponding to the target object; wherein the local remaining flow token is the remaining flow token in the flow token of the flow limiting indicator of the target object allocated by the QoS management end to the QoS client.

[0042] In a fourth aspect, the present application further provides a service request processing device, the device being configured in a QoS server, the device comprising:

[0043] The issuing module is used to issue corresponding token information to each QoS client, so that each QoS client determines whether to perform flow limiting processing on the received service access request based on the corresponding token information and the demand flow token of the flow limiting indicator corresponding to the object targeted by the received service access request;

[0044] Among them, the token information corresponding to each QoS client includes the flow token of the flow limiting indicator corresponding to the access restriction object associated with the QoS client; the access restriction object is an object in the distributed storage system that requires flow access restriction.

[0045] In a fifth aspect, the present application also provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the processor implements the steps of the various business request processing methods described in the first aspect, or implements the steps of the various business request processing methods described in the second aspect.

[0046] In the sixth aspect, the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the various business request processing methods described in the first aspect are implemented, or the steps of the various business request processing methods described in the second aspect are implemented.

[0047] In the seventh aspect, the present application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the steps of the various business request processing methods described in the first aspect above, or implements the steps of the various business request processing methods described in the second aspect above.

[0048] The above-mentioned service request processing method, device and computer equipment obtain a target service access request for a target object in a distributed storage system; and determine the demand flow token for the flow limiting indicator corresponding to the target object when accessing the target object; and then determine whether to perform flow limiting processing on the target service access request based on the demand flow token and the local remaining flow token of the flow limiting indicator corresponding to the target object. In the above scheme, since the local remaining flow token is the remaining flow token in the flow token of the flow limiting indicator for the target object allocated by the QoS management end to the QoS client. When determining whether it is necessary to limit the flow of the target service request, the QoS client can determine it based on the demand flow token and the local remaining flow token without interacting with the QoS management end, thereby avoiding the additional consumption of network resources due to the QoS client asking the QoS management end for the flow limiting query message, and then ensuring the performance of the distributed storage system while being able to limit the flow of service processing requests. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 An application environment diagram of a business request processing method in an embodiment;

[0050] Figure 2 A schematic diagram of a method for limiting the flow of business requests in a conventional technology in an embodiment;

[0051] Figure 3 A schematic diagram of a process flow of a service request processing method in an embodiment;

[0052] Figure 4 A schematic diagram of a process for determining to limit the flow of target service access requests in another embodiment;

[0053] Figure 5 A schematic diagram of a process for processing a target service access request for current limiting in one embodiment;

[0054] Figure 6 A schematic diagram of a process of receiving corresponding token information sent by a QoS management terminal in one embodiment;

[0055] Figure 7 A schematic diagram of a process for sending corresponding token information to each QoS client in an embodiment;

[0056] Fig. 8A This is a schematic diagram of token injection with a service reporting period of 1 second in an embodiment;

[0057] Figure 8B This is a schematic diagram of token injection with a service reporting period of 100ms in an embodiment;

[0058] Fig. 9 A flowchart of another method for processing a service request in an embodiment;

[0059] Fig.10 is a structural block diagram of a service request processing device in one embodiment;

[0060] Fig.11 is a structural block diagram of a service request processing device in another embodiment;

[0061] Fig.12 is an internal structure diagram of a computer device in one embodiment;

[0062] Fig.13 FIG. 4 is a diagram showing the internal structure of a computer device in another embodiment. DETAILED DESCRIPTION

[0063] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0064] The service request processing method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown, it is specifically applied to the application scenario of limiting the flow of business access requests.

[0065] Exemplarily, a distributed storage system connects multiple storage devices through a network to form a unified, scalable storage resource pool, providing data storage and access services to the outside world. Each business access request can access the same distributed storage system through different client nodes. In order to prevent the distributed storage system from crashing due to overload, when the business access request traffic exceeds the load capacity of the distributed storage system, it is necessary to limit the flow of business access requests.

[0066] Optional, see Figure 2 , Figure 2A method for limiting the flow of business requests in traditional technology is provided. That is, the QoS MGR in the distributed storage system performs flow limiting management on each business access request. Specifically, when the business access request (business IO request) reaches the client, the client first interacts with the QoS MGR to determine whether the current business access request is limited. When the scale of the distributed storage system is relatively large, for example, when the storage nodes reach tens of thousands, as the business pressure increases, the amount of flow limiting query messages between the client and the QoS MGR is very large, and the additional consumption of flow limiting query message processing and network resources will seriously affect normal business performance.

[0067] Based on this, the embodiment of the present application provides a method for processing a service request. Figure 1 In the embodiment of the present application, a Qos Client module is deployed on the client, and a Qos MGR module is deployed on the upper end of the storage system. Qos MGR is responsible for allocating traffic tokens (called local traffic tokens) to each QosClient, and Qos Client is responsible for scheduling local traffic tokens. When a service access request arrives at the client, the client obtains the local remaining traffic token of the flow limiting indicator corresponding to the target object of the service access request from the Qos Client module, and determines whether it is necessary to limit the flow of the service access request based on the demand traffic token and the local remaining traffic token corresponding to the target object of the service access request. There is no need to interact with the QoS management end, thereby avoiding the additional consumption of network resources due to the QoS client asking the QoS management end for flow limiting query messages, thereby ensuring the performance of the distributed storage system while being able to limit the flow of service processing requests.

[0068] In one embodiment, Figure 3 As shown, a business request processing method is provided, which is applied to Figure 1 The QoS client in the example is used to illustrate the following steps:

[0069] S301: Obtain a target service access request for a target object in a distributed storage system.

[0070] Exemplarily, a distributed storage system is a storage method that stores data in a dispersed manner on multiple physical nodes, and these nodes are connected together through a network to form a distributed storage system. In a distributed storage system, data can be stored in a variety of forms, for example, data can be stored in storage methods such as files, blocks, and objects. Among them, different access restriction objects can be set for different storage methods. For example, for a file storage method, the access restriction object set can be at least one of a file system, a directory, a user, a user group, and a protocol for interconnection between networks (Internet Protocol, IP); and the access restriction object set can freely combine the file system, directory, user, user group, and IP according to usage requirements. For example, the combination of determined access restriction objects can be file system + user, file system + user group, file system + IP, directory + user, directory + user group, directory + IP, etc.

[0071] Similarly, for block storage, the restricted access object can be a logical unit number (LUN), a consistency group, or a combination of LUN and consistency group. For object storage, the restricted access object can be a bucket, account, user, user group, or a free combination of buckets, accounts, users, and user groups.

[0072] In this way, access restriction objects can be flexibly set according to actual usage, enriching the way to limit the flow of business access requests.

[0073] The target service access request is any one of the service access requests received by the QoS client. The target object is the data or data group stored in the distributed storage system accessed by the target service access request. For example, the target object is a file stored in the distributed storage system.

[0074] S302, determining a required flow token for a flow limiting indicator corresponding to the target object when accessing the target object.

[0075] Exemplarily, the QoS client can determine the demand flow token for the flow limiting indicator corresponding to the target object when accessing the target object based on the access request information corresponding to the target service access request. The flow limiting indicator corresponding to the target object can be bandwidth or input / output operations per second (IOPS), or bandwidth and IOPS. For example, the QoS client can determine the demand flow token corresponding to the required bandwidth and the demand flow token corresponding to the required IOPS when accessing a file based on the access request information corresponding to the target service access request.

[0076] It should be noted that in the embodiment of the present application, the demand traffic token corresponding to the bandwidth required for accessing a file can be determined based on the conversion relationship between bandwidth and traffic tokens. Similarly, the demand traffic token corresponding to the IOPS required for accessing a file can also be determined based on the conversion relationship between IOPS and traffic tokens. For example, the conversion relationship between bandwidth and traffic tokens can be that a bandwidth-type traffic token represents 1KB. If the bandwidth required to access a file is 100KB / s, the number of bandwidth-type traffic tokens required is 100KB. The conversion relationship between IOPS and traffic tokens can be that an IOPS-type traffic token represents a standard IO (4KB). It can be understood that every time a 4KB data block is read or written, it is equivalent to consuming an IOPS-type traffic token.

[0077] S303: Determine whether to perform flow limiting processing on the target service access request according to the demand flow token and the local remaining flow token of the flow limiting indicator corresponding to the target object.

[0078] Exemplarily, the local remaining traffic token is the remaining traffic token in the traffic token of the flow limiting indicator for the target object allocated by the QoS management end to the QoS client. For example, the QoS management end allocates traffic tokens of each flow limiting indicator of each access restricted object to the QoS client in each token issuance cycle. For example, the QoS management end allocates traffic tokens of the bandwidth type corresponding to accessing a certain file and traffic tokens of the IOPS type corresponding to accessing a certain file to the QoS client in each token issuance cycle. Within a token issuance cycle, other business access requests will also access the target object. Then, the remaining traffic tokens in the traffic token of the flow limiting indicator for the target object corresponding to a token issuance cycle are the local remaining traffic tokens.

[0079] For example, if in a token issuance cycle, the bandwidth type traffic token data volume issued by the QoS client to the QoS management end for a certain file is 100KB, and the bandwidth type traffic token data volume consumed by other business access requests to access the file is 20KB, then the remaining bandwidth type traffic token data volume is 80KB. Similarly, if in a token issuance cycle, the IOPS type traffic token data volume issued by the QoS client to the QoS management end for a certain file is 50KB, and the IOPS type traffic token data volume consumed by other business access requests to access the file is 20KB, then the remaining bandwidth type traffic token data volume is 30KB.

[0080] Furthermore, it is possible to determine whether to perform flow limiting processing on the target service access request based on the demand flow token and the local remaining flow token of the flow limiting indicator corresponding to the target object. For example, for each flow limiting indicator corresponding to the target object, based on the size relationship between the demand flow token corresponding to each flow limiting indicator type and the local remaining flow token, determine whether the local remaining flow token corresponding to each flow limiting indicator type is sufficient; if the local remaining flow token corresponding to each flow limiting indicator type is sufficient, it is determined that the target service access request does not need to be flow limited; otherwise, it is determined that the target service access request needs to be flow limited.

[0081] The above-mentioned service request processing method obtains a target service access request for a target object in a distributed storage system; and determines the demand flow token for the flow limiting indicator corresponding to the target object when accessing the target object; and then determines whether to perform flow limiting processing on the target service access request based on the demand flow token and the local remaining flow token of the flow limiting indicator corresponding to the target object. In the above scheme, since the local remaining flow token is the remaining flow token in the flow token of the flow limiting indicator for the target object allocated by the QoS management end to the QoS client. When determining whether it is necessary to limit the flow of the target service request, the QoS client can determine it based on the demand flow token and the local remaining flow token without interacting with the QoS management end, thereby avoiding the additional consumption of network resources due to the QoS client asking the QoS management end for the flow limiting query message, and then ensuring the performance of the distributed storage system while being able to limit the flow of service processing requests.

[0082] In some optional implementations, see Figure 4 , Figure 4 Another flowchart for determining whether to perform flow limiting processing on a target service access request is provided, which specifically includes the following steps:

[0083] S401, comparing the demand flow token corresponding to each flow limiting indicator with the local remaining flow token.

[0084] Exemplarily, the demand flow token corresponding to each flow limiting indicator may be compared with the local remaining flow token to determine whether the demand flow token corresponding to each flow limiting indicator is greater than the local remaining flow token.

[0085] S402: If the required flow token corresponding to any flow limiting indicator is greater than the local remaining flow token, it is determined that the target service access request needs to be flow limited.

[0086] Furthermore, if the demand flow token corresponding to any flow limiting indicator is greater than the local remaining flow token, it means that the local remaining flow token of the flow limiting indicator is insufficient to support the target business access request to access the target object, and the target business access request needs to be flow limited.

[0087] In an embodiment of the present application, by comparing whether the demand flow token corresponding to each flow limiting indicator of the target object is greater than the local remaining flow token, if there is any flow limiting indicator corresponding to a demand flow token greater than the local remaining flow token, it is determined that the target business access request needs to be flow limited, thereby avoiding the problem of access to the target object being blocked when the access flow of a certain flow limiting indicator of the target object is greater than the flow target.

[0088] Optionally, in the above embodiment, the target service access request is subjected to flow limiting processing, which may be to add the target service access request to a waiting queue to wait for the local remaining traffic tokens of the flow limiting indicator corresponding to the target object in the QoS client to satisfy the required traffic tokens, and then continue to process the target service access request.

[0089] In the embodiment of the present application, by adding the target service access request to the waiting queue, the target service access request is subjected to flow limiting processing, thereby avoiding the problem of access congestion caused by the flow of accessing the target object exceeding the target flow.

[0090] Furthermore, after adding the target service access request to the waiting queue, it is necessary to continue processing the target service access request when the local remaining traffic tokens can meet the required traffic tokens. For the specific implementation process, see Figure 5 , Figure 5 A flowchart of processing a target service access request for flow control is provided, which specifically includes the following steps:

[0091] S501, if a new traffic token for the flow limiting indicator of the target object issued by the QoS management end is received, and / or a traffic token release event for the flow limiting indicator corresponding to the target object is detected by other business access requests, the local remaining traffic tokens of the flow limiting indicator corresponding to the target object are updated.

[0092] For example, in the next token issuance cycle, the QoS management end will re-issue a new traffic token for the flow limiting indicator of the target object to the QoS client. At this time, the local remaining traffic token of the flow limiting indicator corresponding to the target object can be updated.

[0093] Optionally, in the same token issuance cycle, after other business access requests complete access to the target object, the flow token of the flow limit indicator corresponding to the target object will be released, and the local remaining flow token of the flow limit indicator corresponding to the target object will also be updated. That is, if the flow token release event of the flow limit indicator corresponding to the target object is detected by other business access requests, the local remaining flow token of the flow limit indicator corresponding to the target object can also be updated.

[0094] S502: When the updated local remaining traffic token is greater than or equal to the required traffic token, extract the target service access request from the waiting queue.

[0095] Furthermore, after updating the local remaining traffic token, the demand traffic token corresponding to each flow limiting indicator corresponding to the target object is repeatedly compared with the local remaining traffic token. If the local remaining traffic token corresponding to each flow limiting indicator is greater than or equal to the demand traffic token, that is, when the updated local remaining traffic token is greater than or equal to the demand traffic token, it can be considered that the local remaining traffic token corresponding to each flow limiting indicator at this time can support the target business request to access the target object, thereby extracting the target business access request from the waiting queue.

[0096] S503, allocating a demand flow token to the target service access request, and accessing the target object based on the allocated demand flow token.

[0097] Furthermore, a demand flow token is allocated to the target service access request, that is, a demand flow token corresponding to each flow limiting indicator is allocated, and the target object is accessed based on the allocated demand flow token.

[0098] In an embodiment of the present application, when the local remaining traffic token is updated, it continues to be determined whether the local remaining traffic token can satisfy the target business access request to access the target object, thereby minimizing the waiting time for the target business access request to be processed and speeding up the efficiency of processing the target business access request.

[0099] In some optional implementations, the local remaining traffic token in the above embodiment can be understood as the remaining traffic token in the traffic token of the flow limit indicator for the target object allocated by the QoS management end to the QoS client in the current service reporting period. Based on this, see Figure 6 , Figure 6 A schematic diagram of a process for receiving corresponding token information issued by a QoS management terminal is provided, which specifically includes the following steps:

[0100] S601, determining service information of a current service reporting period according to a total flow token of a flow limiting indicator corresponding to an access restriction object of each service access request received by a QoS client in a previous service reporting period.

[0101] Exemplarily, the access restriction object is an object in a distributed storage system that needs to be subject to traffic access restriction, and the access restriction object includes at least the target object. The QoS client reports service information to the QoS management terminal in each service reporting cycle. Service information may include service performance and service congestion. Service performance can be understood as the total traffic tokens consumed by the service access requests actually processed by the QoS client for the flow limiting indicator of each access restriction object; service congestion can be understood as the total traffic tokens required by the service access requests limited by the QoS client for the flow limiting indicator of each access restriction object; the total traffic tokens consumed by the service access requests actually processed by the QoS client for the flow limiting indicator of each access restriction object and the total traffic tokens required by the service access requests limited by the QoS client for the flow limiting indicator of each access restriction object are used as the total traffic tokens of the flow limiting indicators corresponding to the access restriction objects for each service access request received by the QoS client.

[0102] For example, if the total traffic tokens consumed by the bandwidth of the file for the service access requests actually processed by the QoS client in the previous service reporting cycle are 100KB; and the total traffic tokens required for the bandwidth of the file for the service access requests added to the waiting queue by the QoS client in the previous service reporting cycle are 50KB, then the total traffic tokens for the bandwidth corresponding to the file for each service access request received by the QoS client are 150KB. Then the total traffic tokens of each flow limiting indicator corresponding to the same access restriction object for each service access request received by the QoS client can be used as the service information of the current service reporting cycle, that is, the service information can reflect the total traffic tokens of each flow limiting indicator corresponding to each access restriction object for each service access request received by the QoS client, so that the QoS management end sends the traffic tokens of each flow limiting indicator corresponding to each access restriction object to the QoS client according to the service information.

[0103] S602: Report the service information to the QoS management terminal, so that the QoS management terminal determines the token information corresponding to each QoS client in the current service reporting period based on the service information reported by each QoS client.

[0104] Exemplarily, the QoS client reports service information to the QoS management end, so that the QoS management end determines the token information corresponding to each QoS client in the current service reporting period based on the service information reported by each QoS client. For example, the QoS management end stores the flow tokens of each flow limiting indicator corresponding to each access restriction object. For the case where the access restriction object is a file, if the number of flow tokens of the bandwidth type for accessing the file stored by the QoS management end is 500KB, the service information reported by QoS client 1 to the QoS management end indicates that the number of flow tokens of the bandwidth type that QoS client 1 needs to access the file is 200KB, and the service information reported by QoS client 1 to the QoS management end indicates that the number of flow tokens of the bandwidth type that QoS client 2 needs to access the file is 300KB; then the QoS management end can send 200KB of flow tokens of the bandwidth type for accessing the file to QoS client 1 in one token issuance period, and send 300KB of flow tokens of the bandwidth type for accessing the file to QoS client 2.

[0105] S603: Receive corresponding token information sent by the QoS management terminal.

[0106] Furthermore, the QoS client receives the corresponding token information sent by the QoS management terminal, wherein the token information includes the flow token of the flow limiting indicator corresponding to the access restriction object.

[0107] In an embodiment of the present application, the QoS management end reports service information to the QoS client in each service reporting cycle, so that the QoS management end determines to send corresponding token information to the QoS client based on the service information, which can make more full use of traffic tokens and improve the processing efficiency of service access requests.

[0108] In some optional implementations, the present application provides another service request processing method, which is applied to Figure 1 Taking the QoS server in as an example, the specific implementation process is as follows:

[0109] Exemplarily, corresponding token information is sent to each QoS client, so that each QoS client determines whether to perform flow limiting processing on the received service access request based on the corresponding token information and the demand flow token of the flow limiting indicator corresponding to the object targeted by the received service access request. For example, the QoS server can send the corresponding token information to the QoS client according to a preset token distribution ratio, or send the corresponding token information to the QoS client according to the actual demand of the QoS client for the flow token.

[0110] Optionally, each QoS client may issue the corresponding token information in accordance with the following principles:

[0111] 1) Traffic tokens are not allocated to QoS clients that have not reported service information and have no service access requests; failure to report can be understood as failure to report service information for several consecutive cycles. If service information is not reported in only one reporting cycle, it can be issued according to the service information of the previous reporting cycle to avoid failure to successfully report service information due to temporary network instability in the QoS client, which in turn leads to failure to issue a traffic token to the QoS client.

[0112] 2) The sum of local traffic tokens allocated to all QoS clients cannot be greater than the total number of traffic tokens of QoS clients.

[0113] 3) When there are sufficient tokens, traffic tokens can be allocated according to the demand ratio of each QoS client.

[0114] 4) When tokens are insufficient, the same preset number of traffic tokens can be issued to the QoS clients. For example, 100KB of traffic tokens can be issued to the QoS clients involved in the same access restriction object, and the remaining traffic tokens can be allocated to the QoS clients involved in the same access restriction object according to the demand ratio.

[0115] Among them, the token information corresponding to each QoS client includes the flow token of the flow limiting indicator corresponding to the access restriction object associated with the QoS client; the access restriction object is the object in the distributed storage system that needs to be subject to flow access restriction. Exemplarily, the access restriction object associated with the QoS client can be understood as the object that needs to be accessed by the service access request received by the QoS client. The access restriction objects associated with different QoS clients may be the same or different. Therefore, only the flow token of the flow limiting indicator corresponding to the access restriction object associated with the QoS client can be sent to the QoS client.

[0116] In an embodiment of the present application, the QoS server sends a traffic token to the QoS client. When determining whether it is necessary to limit the flow of service access requests, it only needs the QoS client's required traffic token and the local remaining traffic token to determine it, without the need to interact with the QoS management end, thereby avoiding the additional consumption of network resources due to the QoS client asking the QoS management end for flow limit query messages, and thus ensuring the performance of the distributed storage system while being able to limit the flow of service processing requests.

[0117] Optional, see Figure 7 , Figure 7 A flowchart of sending corresponding token information to each QoS client is provided, which specifically includes the following steps:

[0118] S701, receiving service information reported by each QoS client in the current service reporting period.

[0119] Exemplarily, each QoS client reports service information to the QoS server in the current service reporting cycle. The service information reported by each QoS client is determined based on the total flow token of the flow limiting indicator corresponding to the access restriction object of each service access request received by the QoS client in the previous service reporting cycle.

[0120] S702: Determine the token information corresponding to each QoS client in the current service reporting period according to the service information reported by each QoS client.

[0121] Furthermore, the QoS server can determine the token information corresponding to each QoS client in the current service reporting period based on the service information reported by each QoS client. For example, the QoS server can determine the issuance ratio of the number of traffic tokens corresponding to each QoS client in the current service reporting period based on the service information reported by each QoS client. Specifically, the QoS server can determine the issuance ratio of traffic tokens for the flow limiting indicators corresponding to each access restriction object based on the service information reported by each QoS client; and then determine the total number of traffic tokens for the flow limiting indicators corresponding to each access restriction object issued to each QoS client in the current service reporting period based on the total number and issuance ratio of traffic tokens for the flow limiting indicators corresponding to each access restriction object.

[0122] It should be noted that the length of a service reporting cycle can be determined according to the scale of the distributed storage system. For example, the service reporting cycle can be set to 100ms. In the case of a large-scale distributed storage system, a smaller service reporting cycle will reduce the maximum delay of service access requests and provide more stable performance.

[0123] For example, see Fig. 8A , Fig. 8A A token injection diagram for bandwidth type with a service reporting period of 1s is provided. Assuming that the number of local tokens of the QoS client is 500MB, the token bucket capacity of the QoS client is set to 500MB, and all traffic tokens are injected into the token bucket at a frequency of 1s. It is possible that all tokens are consumed in the first 200ms of service access requests, and the service requests in the next 800ms are limited, resulting in extended service request time and large fluctuations in the performance curve.

[0124] See also Figure 8B , Figure 8BA token injection diagram of a bandwidth type with a service reporting period of 100ms is provided. In order to solve the problem of extended and large fluctuations in service access requests, periodic and continuous injection of traffic tokens can be used. Assuming that the number of local tokens of the QoS client is 500MB, the token injection period is 100ms, and the token bucket capacity is set to 50MB, the upper limit of token consumption per 100ms service is 50MB. In this scenario, the maximum delay of service access requests is less than 100ms, and the performance curve is more stable.

[0125] S703: Send corresponding token information to each QoS client.

[0126] Furthermore, corresponding token information may be issued to each QoS client according to the determined total number of flow tokens corresponding to the flow limiting indicators of each access restriction object issued to each QoS client in the current service reporting period.

[0127] Exemplarily, the QoS server sends corresponding token information to each QoS client, and can directly inject the traffic token into the token bucket corresponding to each QoS client; or, in the case of a limited service access request, it can first be allocated to the limited service access request, and the remaining traffic tokens can be injected into the token bucket.

[0128] In an embodiment of the present application, the corresponding token information to be sent to each QoS client is determined based on the service information reported by each QoS client in the current service reporting period, so that the traffic token can be more fully utilized and the processing efficiency of the service access request can be improved.

[0129] In some optional implementations, see Fig. 9 , Fig. 9 A flowchart of another service request processing method is provided, which specifically includes the following steps:

[0130] S901, determining service information of a current service reporting period according to a total flow token of a flow limiting indicator corresponding to an access restriction object of each service access request received by a QoS client in a previous service reporting period.

[0131] S902: Report service information to the QoS management terminal.

[0132] S903, receiving service information reported by each QoS client in the current service reporting period, and determining token information corresponding to each QoS client in the current service reporting period according to the service information reported by each QoS client.

[0133] S904: Send corresponding token information to each QoS client.

[0134] S905: Receive corresponding token information sent by the QoS management terminal.

[0135] S906: Obtain a target service access request for a target object in the distributed storage system.

[0136] S907, determining a required flow token for a flow limiting indicator corresponding to the target object when accessing the target object.

[0137] S908: Compare the demand flow token corresponding to each flow limiting indicator with the local remaining flow token.

[0138] S909: If the required flow token corresponding to any flow limiting indicator is greater than the local remaining flow token, the target service access request is added to the waiting queue.

[0139] S910, if a new traffic token for the flow limiting indicator of the target object is received from the QoS management end, and / or a traffic token release event for the flow limiting indicator corresponding to the target object is detected by other business access requests, the local remaining traffic tokens of the flow limiting indicator corresponding to the target object are updated.

[0140] S911: When the updated local remaining traffic token is greater than or equal to the required traffic token, extract the target service access request from the waiting queue.

[0141] S912, allocating a demand flow token for the target service access request;

[0142] S913: Access the target object based on the allocated demand traffic token.

[0143] The specific process of S901-S913 above can refer to the description of the above method embodiment, and its implementation principle and technical effect are similar, which will not be repeated here.

[0144] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0145] Based on the same inventive concept, the embodiment of the present application also provides a service request processing device for implementing the service request processing method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the one or more service request processing device embodiments provided below can refer to the limitations on the service request processing method above, and will not be repeated here.

[0146] In one embodiment, Fig.10 As shown, a service request processing device is provided, which is configured in a QoS client and includes:

[0147] An acquisition module 10 is used to acquire a target service access request for a target object in a distributed storage system;

[0148] The first determination module 20 is used to determine the required flow token for the flow limiting indicator corresponding to the target object when accessing the target object; wherein the flow limiting indicator corresponding to the target object includes bandwidth and / or IOPS;

[0149] The second determination module 30 is used to determine whether to perform flow limiting processing on the target service access request based on the demand flow token and the local remaining flow token of the flow limiting indicator corresponding to the target object; wherein the local remaining flow token is the remaining flow token in the flow token of the flow limiting indicator of the target object allocated by the QoS management end to the QoS client.

[0150] The above-mentioned service request processing device obtains a target service access request for a target object in a distributed storage system; and determines the demand flow token for the flow limiting indicator corresponding to the target object when accessing the target object; and then determines whether to perform flow limiting processing on the target service access request based on the demand flow token and the local remaining flow token of the flow limiting indicator corresponding to the target object. In the above scheme, since the local remaining flow token is the remaining flow token in the flow token of the flow limiting indicator for the target object allocated by the QoS management end to the QoS client. When determining whether it is necessary to limit the flow of the target service request, the QoS client can determine it based on the demand flow token and the local remaining flow token without interacting with the QoS management end, thereby avoiding the additional consumption of network resources caused by the QoS client asking the QoS management end for the flow limiting query message, and then ensuring the performance of the distributed storage system while being able to limit the flow of service processing requests.

[0151] In one embodiment, when the current limiting indicator includes bandwidth and IOPS, the second determining module 30 specifically includes:

[0152] A comparison unit, used for comparing the demand flow token corresponding to each flow limiting indicator with the local remaining flow token;

[0153] The flow limiting unit is used to determine that the target service access request needs to be flow limited if the required flow token corresponding to any flow limiting indicator is greater than the local remaining flow token.

[0154] In one embodiment, the current limiting unit is specifically used for:

[0155] Add the target service access request to the waiting queue.

[0156] In one embodiment, the device further includes an access module, and after adding the target service access request to the waiting queue, the access module is used to:

[0157] If a new traffic token for the flow limiting indicator of the target object is received from the QoS management end, and / or a traffic token release event for the flow limiting indicator corresponding to the target object is detected for other business access requests, the local remaining traffic token for the flow limiting indicator corresponding to the target object is updated; when the updated local remaining traffic token is greater than or equal to the demand traffic token, the target business access request is extracted from the waiting queue; the demand traffic token is allocated to the target business access request, and the target object is accessed based on the allocated demand traffic token.

[0158] In one of the embodiments, the local remaining traffic token is the remaining traffic token in the traffic token of the flow limiting indicator for the target object allocated by the QoS management end to the QoS client in the current service reporting period; before obtaining the target service access request for the target object in the distributed storage system, the device also includes a receiving module for:

[0159] Determine the business information of the current business reporting cycle based on the total flow tokens of the flow limiting indicator corresponding to the access restriction object for each business access request received by the QoS client in the previous business reporting cycle; the access restriction object is the object that needs to be subject to flow access restriction in the distributed storage system, and the access restriction object at least includes the target object; report the business information to the QoS management end so that the QoS management end determines the token information corresponding to each QoS client in the current business reporting cycle based on the business information reported by each QoS client; receive the corresponding token information issued by the QoS management end; wherein the token information includes the flow token of the flow limiting indicator corresponding to the access restriction object.

[0160] In one embodiment, Fig.11 As shown, another service request processing device is provided, which is configured in a QoS server and includes:

[0161] The issuing module 40 is used to issue corresponding token information to each QoS client, so that each QoS client determines whether to perform flow limiting processing on the received service access request based on the corresponding token information and the demand flow token of the flow limiting indicator corresponding to the object targeted by the received service access request;

[0162] Among them, the token information corresponding to each QoS client includes the flow token of the flow limiting indicator corresponding to the access restriction object associated with the QoS client; the access restriction object is an object in the distributed storage system that requires flow access restriction.

[0163] In the above-mentioned service request processing device, the QoS server sends a traffic token to the QoS client. When determining whether it is necessary to limit the flow of service access requests, only the QoS client-required traffic token and the local remaining traffic token are needed to determine it, and there is no need to interact with the QoS management end, thereby avoiding the additional consumption of network resources due to the QoS client asking the QoS management end for flow limiting query messages, and thus ensuring the performance of the distributed storage system while being able to limit the flow of service processing requests.

[0164] In one embodiment, the sending module is specifically used for:

[0165] Receive the service information reported by each QoS client in the current service reporting cycle; wherein the service information reported by each QoS client is determined based on the total flow token of the flow limiting indicator corresponding to the access restriction object of each service access request received by the QoS client in the previous service reporting cycle; determine the token information corresponding to each QoS client in the current service reporting cycle based on the service information reported by each QoS client; and send the corresponding token information to each QoS client.

[0166] Each module in the above-mentioned service request processing device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module above.

[0167] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Fig.12As shown. The computer device includes a processor, a memory, a communication interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a service request processing method is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covered on the display screen, or a key, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0168] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Fig.13 As shown. The computer device includes a processor, a memory and a network interface connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store traffic token data. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a service request processing method is implemented.

[0169] Those skilled in the art will understand that Fig.12 , 13 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0170] In one embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps of the service request processing method described in any of the above embodiments when executing the computer program.

[0171] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the service request processing method described in any of the above embodiments are implemented.

[0172] In one embodiment, a computer program product is provided, including a computer program, which implements the steps of the service request processing method described in any of the above embodiments when executed by a processor.

[0173] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0174] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited to this.

[0175] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0176] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be construed as limiting the scope of the present application. It should be noted that, for a person of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for processing a business request, characterized in that: The method is applied to a quality of service (QoS) client, and the method comprises: Obtain a target business access request for a target object in a distributed storage system; Determine a demand flow token for a flow limiting indicator corresponding to the target object when accessing the target object; wherein the flow limiting indicator corresponding to the target object includes bandwidth and / or IOPS; Determine whether to perform flow limiting processing on the target service access request based on the demand flow token and the local remaining flow token of the flow limiting indicator corresponding to the target object; wherein the local remaining flow token is the remaining flow token in the flow token of the flow limiting indicator of the target object allocated by the QoS management end to the QoS client.

2. The method according to claim 1, characterized in that In the case where the flow limiting indicator includes bandwidth and IOPS, determining whether to perform flow limiting processing on the target service access request according to the demand flow token and the local remaining flow token of the flow limiting indicator corresponding to the target object includes: Compare the demand flow token corresponding to each flow limiting indicator with the local remaining flow token; If there is any flow-limiting indicator corresponding to a demand flow token that is greater than the local remaining flow token, it is determined that the target service access request needs to be flow-limited.

3. The method according to claim 1, characterized in that: The target service access request is subjected to flow limiting processing, including: The target service access request is added to a waiting queue.

4. The method according to claim 3, characterized in that After adding the target service access request to the waiting queue, the method further includes: If a new flow token for the flow limiting indicator of the target object is received from the QoS management terminal, and / or a flow token release event for the flow limiting indicator corresponding to the target object is detected by other service access requests, the local remaining flow token of the flow limiting indicator corresponding to the target object is updated; When the updated local remaining traffic token is greater than or equal to the demand traffic token, extracting the target service access request from the waiting queue; The demand flow token is allocated to the target service access request, and the target object is accessed based on the allocated demand flow token.

5. The method according to claim 1, characterized in that The local remaining traffic token is the remaining traffic token in the traffic token of the flow limiting indicator of the target object allocated by the QoS management end to the QoS client in the current service reporting period; Before obtaining the target service access request for the target object in the distributed storage system, the method further includes: Determine the service information of the current service reporting cycle according to the total flow token of the flow limiting indicator corresponding to the access restriction object of each service access request received by the QoS client in the previous service reporting cycle; the access restriction object is an object in the distributed storage system that needs to be subject to flow access restriction, and the access restriction object at least includes the target object; Reporting the service information to the QoS management end, so that the QoS management end determines the token information corresponding to each QoS client in the current service reporting period based on the service information reported by each QoS client; Receive the corresponding token information sent by the QoS management end; wherein the token information includes the flow token of the flow limiting indicator corresponding to the access restriction object.

6. A method for processing a business request, characterized in that: The method is applied to a QoS service end, and the method comprises: Send corresponding token information to each QoS client, so that each QoS client determines whether to perform flow limiting processing on the received service access request based on the corresponding token information and the demand flow token of the flow limiting indicator corresponding to the object targeted by the received service access request; Among them, the token information corresponding to each QoS client includes the flow token of the flow limiting indicator corresponding to the access restriction object associated with the QoS client; the access restriction object is an object in the distributed storage system that requires flow access restriction.

7. The method according to claim 6, characterized in that The sending of corresponding token information to each QoS client includes: Receive service information reported by each QoS client in the current service reporting cycle; wherein the service information reported by each QoS client is determined according to the total flow token of the flow limiting indicator corresponding to the access restriction object of each service access request received by the QoS client in the previous service reporting cycle; Determine, according to the service information reported by each QoS client, the token information corresponding to each QoS client in the current service reporting period; Send the corresponding token information to each QoS client.

8. A service request processing device, characterized in that: The device is configured in a QoS client, and the device includes: An acquisition module, used to acquire a target service access request for a target object in a distributed storage system; A first determination module is used to determine a demand flow token for a flow limiting indicator corresponding to the target object when accessing the target object; wherein the flow limiting indicator corresponding to the target object includes bandwidth and / or IOPS; The second determination module is used to determine whether to perform flow limiting processing on the target service access request based on the demand flow token and the local remaining flow token of the flow limiting indicator corresponding to the target object; wherein the local remaining flow token is the remaining flow token in the flow token of the flow limiting indicator of the target object allocated by the QoS management end to the QoS client.

9. A service request processing device, characterized in that: The device is configured in a QoS server, and the device includes: The issuing module is used to issue corresponding token information to each QoS client, so that each QoS client determines whether to perform flow limiting processing on the received service access request based on the corresponding token information and the demand flow token of the flow limiting indicator corresponding to the object targeted by the received service access request; Among them, the token information corresponding to each QoS client includes the flow token of the flow limiting indicator corresponding to the access restriction object associated with the QoS client; the access restriction object is an object in the distributed storage system that requires flow access restriction.

10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the processor implements the steps of the method according to any one of claims 1 to 5, or implements the steps of the method according to any one of claims 6 to 7.

Images