Request processing method, device, equipment and storage medium of a storage system

Abstract

The present invention discloses a method, apparatus, device and computer-readable storage medium for request processing in a storage system. The method includes: detecting a target request in the acquired request; wherein the target request is a request for a target query interface; determining whether the query result cache corresponding to the target query interface has been enabled; wherein the query result cache stores query results corresponding to requests of the target query interface; if so, obtaining the query result corresponding to the target request according to the query result in the query result cache. By obtaining the query result corresponding to the target request according to the query result in the query result cache, the present invention can utilize the query results of the target query interface cached in advance to query the query results corresponding to the requests of the target query interface, so as to reduce the query process on the nodes in the storage cluster, thereby reducing the query time of the storage system, ensuring the timeliness of the interfaces of the third-party system, and improving the user experience.

Description

Technical Field

[0001] The present invention relates to the technical field of storage system management, and particularly to a request processing method, device, equipment and computer-readable storage medium for a storage system. Background Art

[0002] With the increasing applications of current storage clusters, some storage clusters need to provide interfaces for third-party systems of customers to use and may be frequently called. In the case of a large cluster scale and frequent calls, it may exceed the bearing capacity of the storage system, resulting in a series of problems such as slower response, timeouts, and higher resource occupancy.

[0003] Generally, when a third-party system docks with a storage cluster, it calls the restapi (an interface standard or specification based on the http protocol) interface of the storage system management software, and the storage system management software calls the storage cluster commands in real time for query and configuration; however, as the scale of the storage cluster becomes larger and larger, it is very time-consuming to query all nodes (i.e., storage devices), and the timeliness of the interface provided to the third-party system cannot be guaranteed. As Figure 1 shown, the third-party system can call the storage system management software through the restapi request method, and the storage system management software calls the command line provided by the storage cluster through SSH (Secure Shell, Secure Shell Protocol). This mechanism is simple, but there are the following problems: some commands need to be executed on all nodes, which takes a long time when the cluster scale is large, resulting in a poor user experience; since the requests are placed in a queue waiting to be processed, due to the long processing time of the requests and not ending, a large number of running threads are accumulated in the queue, resulting in an increase in CPU usage, and at the same time, the queue length is also limited, and when the threshold is exceeded, the request may be discarded.

[0004] Therefore, how to reduce the query time of the storage system, ensure the timeliness of the interface of the third-party system, and improve the user experience is an urgent problem to be solved currently. Summary of the Invention

[0005] The object of the present invention is to provide a request processing method, device, equipment and computer-readable storage medium for a storage system to reduce the query time of the storage system, ensure the timeliness of the interface of the third-party system, and improve the user experience.

[0006] To solve the above technical problems, the present invention provides a request processing method for a storage system, including:

[0007] Detecting a target request in the obtained request; wherein, the target request is a request for a target query interface;

[0008] Determine whether the query result cache corresponding to the target query interface has been enabled; wherein, the query result cache stores the query results corresponding to the requests of the target query interface;

[0009] If so, obtain the query result corresponding to the target request according to the query result in the query result cache.

[0010] Optionally, detecting the target request in the obtained request includes:

[0011] Obtain the request of the storage system interface; wherein, the storage system interface includes a query interface and a configuration interface;

[0012] Determine whether the storage system interface corresponding to the request is marked with a target identifier;

[0013] If so, determine the request as the target request.

[0014] Optionally, obtaining the query result corresponding to the target request according to the query result in the query result cache includes:

[0015] Detect whether there is a target query result in the query results in the query result cache; wherein, the target query result is the query result corresponding to the target request;

[0016] If the target query result exists, obtain the target query result from the query result cache;

[0017] If the target query result does not exist, obtain the target query result from the nodes of the storage cluster and store the target query result in the query result cache.

[0018] Optionally, before obtaining the target query result from the query result cache, it further includes:

[0019] Determine whether the target query result in the query result cache is valid;

[0020] If it is valid, execute the step of obtaining the target query result from the query result cache;

[0021] If it is invalid, obtain the target query result from the nodes of the storage cluster and update the target query result in the query result cache.

[0022] Optionally, determining whether the target query result in the query result cache is valid includes:

[0023] Determine whether the storage time of the target query result in the query result cache reaches a threshold;

[0024] If the threshold is reached, it is determined that the target query result in the query result cache is valid, and the step of obtaining the target query result from the query result cache is executed;

[0025] If the threshold is not reached, it is determined that the target query result in the query result cache is invalid, and the step of obtaining the target query result from the nodes of the storage cluster and updating the target query result in the query result cache is executed.

[0026] Optionally, the method further includes:

[0027] Count the interface access volume of the target query interface;

[0028] Determine whether the interface access volume is greater than the opening threshold;

[0029] If it is greater than the opening threshold, the query result cache corresponding to the target query interface is opened.

[0030] Optionally, after determining whether the interface access volume reaches the opening threshold, it further includes:

[0031] If it is not greater than the opening threshold, determine whether the interface access volume is less than the closing threshold;

[0032] If it is less than the closing threshold, the query result cache corresponding to the target query interface is closed.

[0033] The present invention also provides a request processing device for a storage system, including:

[0034] A request detection module, configured to detect a target request in the obtained request; wherein, the target request is a request of a target query interface;

[0035] A cache judgment module, configured to judge whether the query result cache corresponding to the target query interface has been opened; wherein, the query result cache stores the query result corresponding to the request of the target query interface;

[0036] A result acquisition module, configured to, if the query result cache has been opened, obtain the query result corresponding to the target request according to the query result in the query result cache.

[0037] The present invention also provides a request processing device for a storage system, including:

[0038] A memory, configured to store a computer program;

[0039] A processor, configured to execute the steps of the request processing method for the storage system as described above when executing the computer program.

[0040] In addition, the present invention 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 request processing method of the storage system as described above are implemented.

[0041] A request processing method for a storage system provided by the present invention includes: detecting a target request in the acquired request; wherein, the target request is a request for a target query interface; determining whether the query result cache corresponding to the target query interface has been enabled; wherein, the query result cache stores query results corresponding to requests of the target query interface; if so, obtaining the query result corresponding to the target request according to the query result in the query result cache;

[0042] It can be seen that by obtaining the query result corresponding to the target request according to the query result in the query result cache, the present invention can use the query result of the target query interface cached in advance to query the query result corresponding to the request of the target query interface, so as to reduce the query process on the nodes in the storage cluster, thereby reducing the query time of the storage system, ensuring the timeliness of the interfaces of the third-party system, and improving the user experience. In addition, the present invention also provides a request processing device, equipment and computer-readable storage medium for a storage system, which also have the above beneficial effects. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only the embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained according to the provided drawings without creative efforts.

[0044] Figure 1 It is a topological schematic diagram of a storage system;

[0045] Figure 2 It is a flowchart of a request processing method for a storage system provided by an embodiment of the present invention;

[0046] Figure 3 It is an interceptor schematic diagram of another request processing method for a storage system provided by an embodiment of the present invention;

[0047] Figure 4 It is a flowchart schematic diagram of a cache switch interceptor of another request processing method for a storage system provided by an embodiment of the present invention;

[0048] Figure 5 It is a structural block diagram of a request processing device for a storage system provided by an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0049] To make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are some but not all of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0050] Please refer to Figure 2 , Figure 2 , which is a flowchart of a method for processing requests of a storage system provided by an embodiment of the present invention. The method may include:

[0051] Step 101: Detect a target request in the obtained request; where the target request is a request of a target query interface.

[0052] Among them, the request obtained in this step may be a request of a storage system interface, that is, a request sent by a third-party system received through the storage system interface. The target request in this step may be a request of a target query interface in the storage system interface, and the target query interface may be all or part of the query interfaces in the storage system interface, that is, a query interface that can be optimized for querying with the corresponding query result cache.

[0053] Specifically, the interfaces of the storage system in this embodiment (i.e., the storage system interfaces) can be operationally divided into two categories: query interfaces (query) for querying and configuration interfaces (operation) for configuration; in this embodiment, the query speed of the results of the requests of the target query interfaces is improved by setting the cache corresponding to the target query interfaces in the query interfaces (i.e., the query result cache).

[0054] It can be understood that the processor in the request processing device (such as a management node) running the storage system management software in this step can detect and identify whether the obtained request of the storage system interface is a target request, and determine the target request in the obtained request of the storage system interface.

[0055] Specifically, for the specific manner of the target request in the request detected and obtained by the processor in this step, it can be set by the designer according to the practical scenario and user requirements. For example, the processor can obtain the request of the storage system interface; determine whether the storage system interface corresponding to the request is marked with a target identifier; if so, determine the request as the target request; where the storage system interface includes a query interface and a configuration interface. That is to say, in this embodiment, through the setting of the target identifier (such as @EnableCache), it can be marked on the query interface that allows the use of cache (i.e., query result cache). For example, all query interfaces are marked with the target identifier, so as to divide the storage system interface into a query interface that allows the use of cache (i.e., the target query interface) and a configuration interface that does not allow the use of cache.

[0056] Correspondingly, for the non-target requests other than the target requests in the requests obtained by the processor in this embodiment, that is, the processing method of the requests of the interfaces other than the target query interfaces in the storage system interface, it can be implemented in the same or similar manner as the request processing method in the prior art. For example, the corresponding query results can be obtained by real-time query from the nodes of the storage cluster; for example, if the storage system interface corresponding to the obtained request of the storage system interface is not marked with the target identifier, it can be determined that the request is a non-target request, and the query results corresponding to the request can be obtained from the nodes of the storage cluster.

[0057] In this embodiment, when the scale of the storage cluster is small, the processor can directly query the stored data in real time to ensure simplicity, stability, and accurate query results. Before step 101 of the method provided in this embodiment, the processor can determine whether the number of nodes in the storage cluster is greater than a threshold; if so, enter step 101; if not, the query results corresponding to each request can be obtained by real-time query from the nodes of the storage cluster according to the existing request processing method.

[0058] Step 102: Determine whether the query result cache corresponding to the target query interface has been enabled; if so, enter step 103.

[0059] It can be understood that the query result cache in this step can store the query results corresponding to the requests of the target query interface, that is, the query result cache can store the corresponding query results of the target query interface, such as the query results of previous requests. This embodiment does not limit the specific setting of the query result cache. For example, a separate query result cache can be set for each target query interface, that is, each target query interface corresponds to a different query result cache; or a query result cache can be set for all target query interfaces, that is, all target query interfaces correspond to the same query result cache. This embodiment does not make any restrictions on this.

[0060] Specifically, this embodiment demonstrates the request processing of a target request in the obtained requests. For the request processing of other target requests, the same or similar methods provided in this embodiment can be used for implementation, and this embodiment does not impose any restrictions on this.

[0061] Correspondingly, the method provided in this embodiment may further include a switching control process for query result caching. For example, the processor can count the interface access volume of the target query interface; determine whether the interface access volume is greater than the opening threshold; if it is greater than the opening threshold (such as Figure 4 1000 in), then enable the query result caching corresponding to the target query interface; if it is not greater than the opening threshold, this process can be directly ended, or it can be determined whether the interface access volume is less than the closing threshold; if it is less than the closing threshold (such as Figure 4 500 in), then disable the query result caching corresponding to the target query interface; if it is not less than the closing threshold (such as Figure 4 500 in), then this process can be directly ended or return to the step of determining whether the interface access volume is greater than the opening threshold, waiting for the next comparison between the interface access volume of the target query interface and the opening threshold.

[0062] Such as Figure 3 As shown, in this embodiment, an interface statistics interceptor can be designed. Using this interceptor, requests marked with a target identifier (such as @EnableCache) can be statistically counted, and the number of requests currently being processed can be counted. Subsequently, other interceptors (such as the cache switch interceptor) can enable / disable the cache according to the statistical information; the specific logic can be: in the pre-processing of this interface statistics interceptor, all requests are intercepted. If the interface A corresponding to request A is marked with the target identifier, then the access volume count (counting) of interface A is incremented by 1, and then the interface is released for subsequent interceptors to process. When the business processing is completed, the access volume count of interface A is decremented by 1 in the post-processing of this interceptor, that is, after request A is processed, the access volume of interface A is updated; if it is not marked with the target identifier, it means that request A cannot use the cache, then it is directly released without any processing, so that the query results corresponding to each request can be obtained in real time from the nodes of the storage cluster according to the existing request processing method.

[0063] Such as Figure 3 And Figure 4 As shown, in this embodiment, a cache switch interceptor can be designed. Using this interceptor, the cache is determined to be enabled or disabled according to the interface access volume. The specific logic is: first, verify whether the request is allowed to use the cache. If it is not allowed to use the cache, then directly release the request; if it is allowed to use the cache and the interface access volume per minute exceeds 1000 (i.e., the opening threshold), then enable the cache (i.e., the query result cache), and if the interface access volume per minute is lower than 500 (i.e., the closing threshold), then disable the cache.

[0064] It should be noted that for the case where the query result cache corresponding to the target query interface in this step is not enabled, the query result corresponding to the target request can be directly retrieved from the nodes of the storage cluster in the same or similar manner as the request processing method in the prior art.

[0065] Step 103: Obtain the query result corresponding to the target request according to the query result in the query result cache.

[0066] It can be understood that in this step, when the query result cache corresponding to the target query interface is enabled, the processor can use the query result stored in the query result cache to find and obtain the query result corresponding to the target request. For example, it can find the query result of the previous request identical to the target request from the query results of the previous requests in the query result cache, thereby reducing the process of querying the query result corresponding to the target request from the nodes of the storage cluster, reducing the query time of the storage system, and ensuring the timeliness of the interfaces of the third-party systems.

[0067] Specifically, for the specific manner in which the processor in this step obtains the query result corresponding to the target request according to the query result in the query result cache, it can be set by the designer according to the practical scenario and user requirements. For example, the processor can detect whether there is a target query result in the query results in the query result cache; where the target query result is the query result corresponding to the target request; if there is a target query result, obtain the target query result from the query result cache; if there is no target query result, obtain the target query result from the nodes of the storage cluster and store the target query result in the query result cache.

[0068] Correspondingly, before the processor obtains the target query result from the query result cache, it can also determine whether the target query result in the query result cache is valid; if it is valid, obtain the target query result from the query result cache; if it is invalid, obtain the target query result from the nodes of the storage cluster and update the target query result in the query result cache. For example, determine whether the storage time of the target query result in the query result cache reaches a threshold (such as 30s); if it reaches the threshold, determine that the target query result in the query result cache is valid and obtain the target query result from the query result cache; if it does not reach the threshold, determine that the target query result in the query result cache is invalid, obtain the target query result from the nodes of the storage cluster, and update the target query result in the query result cache.

[0069] Such as Figure 3As shown in the figure, in this embodiment, a cache query / update interceptor for managing, querying, detecting expiration, and updating the cache can be designed. After intercepting the request using this interceptor, it is first determined whether the cache (i.e., the query result cache) has been enabled. If the cache has been enabled, an attempt is made to find data that meets the conditions in the cache. If it can be found, it is verified whether the cached data has expired. If it has not expired, the response is directly returned without further processing. If it has expired, the cached data is cleared and the request is released. If it cannot be found, the request is released. After the business processing is completed, the query result is saved to the cache, and the survival time is set to 30s, indicating that the cache result is valid within 30s. Finally, the response is returned.

[0070] Specifically, after this step, it may further include the step of returning the query result corresponding to the target request to the corresponding third-party system, so as to return the query result of the request to the third-party system that sends the request through the storage system interface.

[0071] In this embodiment, by obtaining the query result corresponding to the target request according to the query result in the query result cache, the embodiment of the present invention can use the query result of the pre-cached target query interface to query the query result corresponding to the request of the target query interface, so as to reduce the query process on the nodes in the storage cluster, thereby reducing the query time of the storage system, ensuring the timeliness of the interface of the third-party system, and improving the user experience.

[0072] Corresponding to the above method embodiment, the embodiment of the present invention also provides a request processing device for a storage system. The request processing device for a storage system described below can be correspondingly referred to the method for processing requests for a storage system described above.

[0073] Please refer to Figure 5 , Figure 5 which is a structural block diagram of a request processing device for a storage system provided by the embodiment of the present invention. The device may include:

[0074] A request detection module 10, configured to detect a target request in the obtained request; wherein, the target request is a request for a target query interface;

[0075] A cache determination module 20, configured to determine whether the query result cache corresponding to the target query interface has been enabled; wherein, the query result cache stores the query result corresponding to the request of the target query interface;

[0076] A result acquisition module 30, configured to, if the query result cache has been enabled, obtain the query result corresponding to the target request according to the query result in the query result cache.

[0077] Optionally, the request detection module 10 may include:

[0078] A request acquisition sub-module, used to acquire requests for storage system interfaces; wherein, the storage system interfaces include a query interface and a configuration interface;

[0079] An identification judgment sub-module, used to judge whether the storage system interface corresponding to the request is marked with a target identification; if so, determine the request as a target request.

[0080] Optionally, the result acquisition module 30 may include:

[0081] A cache detection sub-module, used to detect whether there is a target query result in the query results in the query result cache; wherein, the target query result is the query result corresponding to the target request;

[0082] A cache acquisition sub-module, used to, if there is a target query result, acquire the target query result from the query result cache;

[0083] A node acquisition sub-module, used to, if there is no target query result, acquire the target query result from the nodes of the storage cluster and store the target query result in the query result cache.

[0084] Optionally, the cache acquisition sub-module may include:

[0085] A result judgment unit, used to judge whether the target query result in the query result cache is valid;

[0086] A cache acquisition unit, used to, if it is valid, acquire the target query result from the query result cache;

[0087] A node update unit, used to, if it is invalid, acquire the target query result from the nodes of the storage cluster and update the target query result in the query result cache.

[0088] Optionally, the result judgment unit may specifically be used to judge whether the storage time of the target query result in the query result cache reaches a threshold; if it reaches the threshold, send a start signal to the cache acquisition unit; if it does not reach the threshold, send a start signal to the node update unit.

[0089] Optionally, the device may further include:

[0090] A statistics module, used to count the interface access volume of the target query interface;

[0091] An opening judgment module, used to judge whether the interface access volume is greater than an opening threshold;

[0092] A cache opening module, used to, if it is greater than the opening threshold, open the query result cache corresponding to the target query interface.

[0093] Optionally, the device may further include:

[0094] A closing judgment module, configured to judge whether the interface access volume is less than a closing threshold if it is not greater than an opening threshold;

[0095] A cache closing module, configured to close the query result cache corresponding to the target query interface if it is less than the closing threshold.

[0096] In this embodiment, the embodiment of the present invention obtains the query result corresponding to the target request through the result acquisition module 30 according to the query result in the query result cache, and can use the query result of the pre-cached target query interface to query the query result corresponding to the request of the target query interface, so as to reduce the query process on the nodes in the storage cluster, thereby reducing the query time of the storage system, ensuring the timeliness of the interfaces of the third-party system, and improving the user experience.

[0097] Corresponding to the above method embodiment, the embodiment of the present invention further provides a request processing device for a storage system. A request processing device for a storage system described below can be mutually corresponded and referred to with a request processing method for a storage system described above.

[0098] The embodiment of the present invention provides a request processing device for a storage system, including: a memory, configured to store a computer program; a processor, configured to implement the steps of the request processing method for a storage system provided in the above embodiment when executing the computer program.

[0099] Wherein, the request processing device for a storage system provided in this embodiment can be specifically a management node (such as a computer or a server) in a storage cluster, that is, a node running storage system management software.

[0100] Corresponding to the above method embodiment, the embodiment of the present invention further provides a computer-readable storage medium. A computer-readable storage medium described below can be mutually corresponded and referred to with a request processing method for a storage system described above.

[0101] The embodiment of the present invention 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 request processing method for a storage system provided in the above embodiment are implemented.

[0102] The computer-readable storage medium can specifically be various computer-readable storage media such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc that can store program codes.

[0103] The various embodiments in the specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments, and the same or similar parts among the embodiments can be referred to each other. For the devices, equipment, and computer-readable storage media disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the description in the method section.

[0104] The above has introduced in detail a method, device, equipment, and computer-readable storage medium for processing requests in a storage system provided by the present invention. Specific examples are used herein to elaborate on the principles and implementation manners of the present invention. The descriptions of the above embodiments are only used to help understand the method and its core idea of the present invention. It should be noted that for those of ordinary skill in the art in this technical field, without departing from the principle of the present invention, several improvements and modifications can be made to the present invention, and these improvements and modifications also fall within the protection scope of the claims of the present invention.

Claims

1. A method for processing requests in a storage system, characterized in that, Including: When the number of nodes in the storage cluster is greater than the quantity threshold, detecting a target request in the obtained requests; wherein, the target request is a request for a target query interface; the target query interface is a query interface that can perform query optimization by means of a corresponding query result cache; Judging whether the query result cache corresponding to the target query interface has been enabled; wherein, the query result cache stores query results corresponding to requests of the target query interface; If so, detecting whether there is a target query result in the query results in the query result cache; wherein, the target query result is the query result corresponding to the target request; If the target query result exists, obtaining the target query result from the query result cache; If the target query result does not exist, obtaining the target query result from the nodes of the storage cluster and storing the target query result in the query result cache.

2. The method for processing requests of the storage system according to claim 1, wherein The detecting the target request in the obtained requests includes: Obtaining requests of the storage system interface; wherein, the storage system interface includes a query interface and a configuration interface; Judging whether the storage system interface corresponding to the request is marked with a target identifier; If so, determining the request as the target request.

3. The request processing method of the storage system according to claim 1, wherein Before obtaining the target query result from the query result cache, it further includes: Judging whether the target query result in the query result cache is valid; If it is valid, performing the step of obtaining the target query result from the query result cache; If it is invalid, obtaining the target query result from the nodes of the storage cluster and updating the target query result in the query result cache.

4. The request processing method of the storage system according to claim 3, characterized in that, The judging whether the target query result in the query result cache is valid includes: Judging whether the storage time of the target query result in the query result cache reaches a threshold; If it reaches the threshold, determining that the target query result in the query result cache is valid and performing the step of obtaining the target query result from the query result cache; If it does not reach the threshold, determining that the target query result in the query result cache is invalid and performing the step of obtaining the target query result from the nodes of the storage cluster and updating the target query result in the query result cache.

5. The request processing method of the storage system according to any one of claims 1 to 4, characterized in that, It further includes: Counting the interface access volume of the target query interface; Judging whether the interface access volume is greater than an opening threshold; If it is greater than the opening threshold, enabling the query result cache corresponding to the target query interface.

6. The request processing method of the storage system according to claim 5, wherein After judging whether the interface access volume reaches the opening threshold, it further includes: If it is not greater than the opening threshold, judging whether the interface access volume is less than a closing threshold; If it is less than the closing threshold, closing the query result cache corresponding to the target query interface.

7. A request processing device for a storage system, characterized in that, Including: A request detection module, configured to detect a target request in the obtained requests when the number of nodes in the storage cluster is greater than the quantity threshold; wherein, the target request is a request for a target query interface; the target query interface is a query interface that can perform query optimization by means of a corresponding query result cache; A cache judgment module, configured to judge whether the query result cache corresponding to the target query interface has been enabled; wherein, the query result cache stores the query results corresponding to the requests of the target query interface. A result acquisition module, configured to, if the query result cache has been enabled, acquire the query result corresponding to the target request according to the query result in the query result cache. Wherein, the result acquisition module includes: A cache detection sub-module, configured to detect whether there is a target query result in the query results in the query result cache; wherein, the target query result is the query result corresponding to the target request. A cache acquisition sub-module, configured to, if there is the target query result, acquire the target query result from the query result cache. A node acquisition sub-module, configured to, if there is no target query result, acquire the target query result from the nodes of the storage cluster and store the target query result into the query result cache.

8. A request processing device for a storage system, characterized in that, It includes: A memory, configured to store a computer program. A processor, configured to implement the steps of the request processing method of the storage system according to any one of claims 1 to 6 when executing the computer program.

9. A computer-readable storage medium, characterized in that, A computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the request processing method of the storage system according to any one of claims 1 to 6 are implemented.

Images