Cloud disk operation request processing method and device, equipment and medium

Abstract

The invention relates to a cloud disk operation request processing method and device, equipment and a medium. The cloud disk operation request processing method comprises the following steps: receiving a cloud disk operation request of a user; sending the cloud disk operation request to a target cluster queue through the cluster management node; and sending the cloud disk operation request to the target service node through the target cluster queue, so that the target service node processes the cloud disk operation request. According to the embodiment of the invention, the cloud disk operation request can be processed through the normal target service node, and the operation requirement of a user is met.

Description

Technical Field

[0001] The present disclosure relates to the field of database technology, and in particular to a method, device, equipment and medium for processing a cloud disk operation request. Background Art

[0002] Currently, after a cloud disk is created, the database will record the host information and availability zone (AZ) information of the cloud disk. When a user makes an operation request for the cloud disk, the request receiving node directly sends the request to the corresponding message queue through the host information, and the message queue sends it to the corresponding service node for processing.

[0003] However, the service node of the cloud disk is strongly dependent on the Host information for related operations. If the service node fails and cannot be restored, the service node determined by the Host information cannot process the operation request, and other service nodes cannot be determined by the Host information, thereby failing to meet user operation requirements. Summary of the invention

[0004] In order to solve the above technical problems, the present disclosure provides a cloud disk operation request processing method, device, equipment and medium.

[0005] In a first aspect, the present disclosure provides a method for processing a cloud disk operation request, comprising:

[0006] Receive the user's cloud disk operation request;

[0007] Send the cloud disk operation request to the target cluster queue through the cluster management node;

[0008] The cloud disk operation request is sent to the target service node through the target cluster queue, so that the target service node processes the cloud disk operation request.

[0009] In a second aspect, the present disclosure provides a cloud disk operation request processing device, including:

[0010] A request receiving module, used to receive a user's cloud disk operation request;

[0011] A first sending module is used to send the cloud disk operation request to the target cluster queue through the cluster management node;

[0012] The second sending module is used to send the cloud disk operation request to the target service node through the target cluster queue, so that the target service node processes the cloud disk operation request.

[0013] In a third aspect, the present disclosure provides a cloud disk operation request processing device, including:

[0014] processor;

[0015] A memory for storing executable instructions;

[0016] The processor is used to read executable instructions from the memory and execute the executable instructions to implement the cloud disk operation request processing method of the first aspect.

[0017] In a fourth aspect, the present disclosure provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the processor implements the cloud disk operation request processing method of the first aspect.

[0018] Compared with the prior art, the technical solution provided by the embodiments of the present disclosure has the following advantages:

[0019] The cloud disk operation request processing method, apparatus, device and medium of the disclosed embodiments can receive a user's cloud disk operation request, then send the cloud disk operation request to a target cluster queue through a cluster management node, and finally send the cloud disk operation request to a target service node through the target cluster queue, so that the target service node processes the cloud disk operation request. Thus, the cloud disk operation request can be sent to the target cluster queue through the cluster management node, and the target cluster queue sends the cloud disk operation request to the target service node for processing, so that the cloud disk operation request can be processed by a normal target service node to meet the user's operation requirements. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale.

[0021] Figure 1 A flowchart of a method for processing a cloud disk operation request provided by an embodiment of the present disclosure;

[0022] Figure 2 A flowchart of another method for processing a cloud disk operation request provided by an embodiment of the present disclosure;

[0023] Figure 3 A schematic diagram of the structure of a cloud disk operation request processing device provided by an embodiment of the present disclosure;

[0024] Figure 4 A schematic diagram of the structure of a cloud disk operation request processing device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0025] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0026] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0027] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.

[0028] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0029] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0030] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0031] In order to solve the above problems, the embodiments of the present disclosure provide a method, device, equipment and medium for processing cloud disk operation requests. Figure 1 to Figure 2 The cloud disk operation request processing method provided by the embodiment of the present disclosure is described in detail.

[0032] Figure 1 A flow chart of a method for processing a cloud disk operation request provided by an embodiment of the present disclosure is shown.

[0033] In the embodiment of the present disclosure, the cloud disk operation request processing method may be executed by a server, wherein the server may include but is not limited to servers such as a cloud server or a cloud server cluster.

[0034] like Figure 1 As shown, the cloud disk operation request processing method may include the following steps.

[0035] S110: Receive a cloud disk operation request from a user.

[0036] In an embodiment of the present disclosure, the server may receive a cloud disk operation request from a user.

[0037] Optionally, the cloud disk operation request may be an operation request for a cloud disk, wherein the cloud disk operation request may include at least one of a deletion operation request, a capacity expansion operation request, and a snapshot operation request.

[0038] Specifically, the user can operate the cloud disk, that is, the user initiates a cloud disk operation request to the server, and the server can receive the cloud disk operation request, wherein the cloud disk operation request may include at least one of a deletion operation request, a capacity expansion operation request, and a snapshot operation request, for example, the server can receive the cloud disk operation request through Cinder-API. Cinder is a component for managing cloud disks.

[0039] S120. Send the cloud disk operation request to the target cluster queue through the cluster management node.

[0040] In an embodiment of the present disclosure, the server may send a cloud disk operation request to a target cluster queue through a cluster management node.

[0041] Optionally, the cluster management node may be a node for managing each cluster queue, wherein the cluster management node has a cluster message subscription function.

[0042] Optionally, the target cluster queue may be a cluster queue that can process the cloud disk operation request.

[0043] Specifically, after receiving the cloud disk operation request, the server can send the cloud disk operation request to the target cluster queue through the cluster management node, for example, sending the cloud disk operation request to the target cluster queue through OpenStack (Topic). Among them, OpenStack is an open source cloud computing management platform project, which is a combination of a series of software open source projects, and Topic is a subscription function.

[0044] S130: Send the cloud disk operation request to the target service node through the target cluster queue, so that the target service node processes the cloud disk operation request.

[0045] In an embodiment of the present disclosure, the server may send the cloud disk operation request to the target service node through the target cluster queue, so that the target service node processes the cloud disk operation request.

[0046] Optionally, the target service node may be a service node that processes a cloud disk operation request.

[0047] Specifically, after the server sends the cloud disk operation request to the target cluster queue through the cluster management node, it can also send the cloud disk operation request to the target service node through the target cluster queue, and the target service node can process the cloud disk operation request. For example, the server can send the cloud disk operation request to the Cinder-Volume service node through the target cluster queue, and the Cinder-Volume service node processes the cloud disk operation request, such as performing corresponding processing on the cloud disk according to at least one of the deletion operation request, expansion operation request, and snapshot operation request. Among them, the Cinder-Volume service node can be one of the Cinder services, and the service node runs on the storage node to manage the storage space.

[0048] Therefore, in the embodiment of the present disclosure, it is possible to receive the user's cloud disk operation request, then send the cloud disk operation request to the target cluster queue through the cluster management node, and finally send the cloud disk operation request to the target service node through the target cluster queue, so that the target service node processes the cloud disk operation request. Therefore, the cloud disk operation request can be sent to the target cluster queue through the cluster management node, and the target cluster queue sends the cloud disk operation request to the target service node for processing, so that the cloud disk operation request can be processed by the normal target service node to meet the user's operation needs.

[0049] Optionally, after S110, the cloud disk operation request processing method may further include: determining a first target type to which the cloud disk operation request belongs; and determining a target cluster queue corresponding to the first target type from a plurality of cluster queues.

[0050] In an embodiment of the present disclosure, the server may determine the first target type to which the cloud disk operation request belongs.

[0051] Optionally, the first target type may be a type used to characterize a cluster queue.

[0052] Optionally, the cluster queue may be a queue including multiple clusters. For example, the type of the cluster queue may be represented by the availability zone AZ information, such as the type of the A cluster queue may be AZ1; the type of the B cluster queue may be AZ2, which is not limited here.

[0053] Specifically, after receiving the cloud disk operation request, the server may determine the first target type to which the cloud disk operation request belongs, for example, determine the available zone information to which the cloud disk operation request belongs.

[0054] Further, the server may determine a target cluster queue corresponding to the first target type from among the multiple cluster queues.

[0055] Optionally, the target cluster queue may be a cluster queue corresponding to the first target type.

[0056] Specifically, after determining the first target type to which the cloud disk operation request belongs, the server can determine the target cluster queue corresponding to the first target type in multiple cluster queues. For example, the server determines that the first target type to which the cloud disk operation request belongs is AZ1, then the cluster queue A corresponding to AZ1 in the multiple cluster queues can be the target cluster queue; the server determines that the first target type to which the cloud disk operation request belongs is AZ2, then the cluster queue B corresponding to AZ2 in the multiple cluster queues can be the target cluster queue. No limitation is made here.

[0057] Thus, the first target type to which the cloud disk operation request belongs can be determined, thereby determining the corresponding target cluster queue, and then sending the request through the target cluster queue to implement processing of the cloud disk operation request.

[0058] Optionally, after S120, the cloud disk operation request processing method may further include: determining a second target type to which the cloud disk operation request belongs; determining a target service node corresponding to the second target type among multiple service nodes, the second target type being used to characterize the type of the service node.

[0059] In an embodiment of the present disclosure, the server may determine the second target type to which the cloud disk operation request belongs.

[0060] Optionally, the second target type may be a type used to characterize a service node.

[0061] Optionally, the service node may be a node for processing cloud disk operation requests. For example, the type of the service node may be represented by a hard disk type, such as the type of service node A may be a solid hard disk SSD3, and the type of service node A may be an mobile hard disk EHDD.

[0062] Specifically, the server may determine the second target type to which the cloud disk operation request belongs, for example, the hard disk type corresponding to the cloud disk operation request.

[0063] Further, after determining the second target type to which the cloud disk operation request belongs, the server may determine a target service node corresponding to the second target type from among multiple service nodes.

[0064] Optionally, the target service node may be a service node corresponding to the second target type.

[0065] Specifically, after determining the second target type to which the cloud disk operation request belongs, the server can determine the target service node corresponding to the second target type among multiple service nodes. For example, the server determines that the second target type to which the cloud disk operation request belongs is a solid hard disk SSD3, then the A service node corresponding to the second target type is determined as the target service node among multiple service nodes; the server determines that the second target type to which the cloud disk operation request belongs is an mobile hard disk EHDD, then the B service node corresponding to the second target type is determined as the target service node among multiple service nodes. No limitation is made here.

[0066] In this way, the second target type to which the cloud disk operation request belongs can be determined, thereby determining the target service node for processing the cloud disk operation request to meet the user operation requirements.

[0067] Optionally, the cloud disk operation request may include a first target type and a second target type. For example, AZ1@SSD3 can be used to indicate that the first target type of the cloud disk operation request is AZ1, and the second target type is SSD3; AZ1@EHDD can be used to indicate that the first target type of the cloud disk operation request is AZ1, and the second target type is EHDD, and so on. No limitation is given here.

[0068] Optionally, S130 may specifically include: based on a polling scheduling strategy, performing polling scheduling on multiple service sub-nodes included in the target service node, so that the service sub-nodes process the cloud disk operation request.

[0069] In the embodiment of the present disclosure, the server may perform polling scheduling on multiple service sub-nodes included in the target service node based on a polling scheduling strategy, so that the service sub-nodes process the cloud disk operation request.

[0070] Optionally, the polling scheduling strategy may be a round-robin query scheduling strategy.

[0071] Optionally, the service subnode may be a subnode in the service node.

[0072] Specifically, after the server sends the cloud disk operation request to the target service node through the target cluster queue, it can perform polling scheduling on the multiple service sub-nodes included in the target service node. For example, the cloud disk operation request may include three requests, such as request A, request B, and request C. The target service node includes sub-node A and sub-node B. The server performs polling scheduling on the service sub-nodes, such as processing request A through sub-node A, processing request B through sub-node B, processing request C through sub-node A, etc. The target service node may include any sub-node, and the cloud disk operation request may include any request, which is not limited here.

[0073] Thus, the cloud disk operation request can be processed through the cloud disk operation request to achieve request load balancing and increase the message response speed.

[0074] Optionally, the cloud disk operation request processing method may further include: in the event of a failure event in a target service subnode among multiple service subnodes, based on a polling scheduling strategy, polling scheduling is performed on the remaining service subnodes among the multiple service subnodes except the target service subnode, so that the remaining service subnodes process the cloud disk operation request.

[0075] In an embodiment of the present disclosure, when a failure event occurs in a target service subnode among multiple service subnodes, the server can perform polling scheduling on the remaining service subnodes among the multiple service subnodes except the target service subnode based on a polling scheduling strategy, so that the remaining service subnodes process the cloud disk operation request.

[0076] Optionally, the fault event may be a shutdown or abnormality event of the target service subnode.

[0077] Specifically, when a target service subnode among multiple service subnodes fails, the server can determine the target service subnode, and after receiving a cloud disk operation request, perform polling scheduling on the remaining service subnodes among the multiple service subnodes except the target service subnode according to the polling scheduling strategy, so that the remaining service subnodes process the cloud disk operation request. For example, the multiple service subnodes may be subnode A and subnode B. When a failure occurs at subnode A, that is, subnode A is the target service subnode, the server can process the cloud disk operation request through subnode B according to the polling scheduling strategy.

[0078] Therefore, in the embodiment of the present disclosure, after a failure event occurs in the target service sub-node, the cloud disk operation request can be processed by the remaining service sub-nodes to meet the user operation requirements.

[0079] Figure 2 A flow chart of another method for processing a cloud disk operation request provided by an embodiment of the present disclosure is shown.

[0080] like Figure 2As shown, the server can receive a cloud disk operation request through Cinder-API, and then send the cloud disk operation request to the cluster management node (OpenStack (Topic)) through Cinder-API, and then through OpenStack (Topic) according to the first target type and the second target type of the cloud disk operation request, for example, AZ1@SSD3 is used to indicate that the first target type of the cloud disk operation request is AZ1, the target cluster queue is determined, the second target type is SSD3, the target service node is determined, and the cloud disk operation request is sent to the target service node. Finally, based on the polling scheduling strategy, the target service node includes multiple service sub-nodes, such as Host1@SSD3, Host2@SSD3, etc., for processing; and AZ1@EHDD is used to indicate that the first target type of the cloud disk operation request is AZ1, the target cluster queue is determined, the second target type is EHDD, the target service node is determined, and the cloud disk operation request is sent to the target service node. Finally, based on the polling scheduling strategy, the target service node includes multiple service sub-nodes, such as Host1@SSD3, Host2@SSD3, etc., for processing.

[0081] Figure 3 A schematic diagram of the structure of a cloud disk operation request processing device provided by an embodiment of the present disclosure is shown.

[0082] like Figure 3 As shown, the cloud disk operation request processing device 300 may include a request receiving module 310 , a first sending module 320 and a second sending module 330 .

[0083] The request receiving module 310 can be used to obtain type information of the object to be placed inside the vehicle.

[0084] The first sending module 320 can be used to track the placement operation of the object to be placed and obtain the placement position information of the object to be placed.

[0085] The second sending module 330 can be used to obtain external information of the vehicle and determine the target object to be picked up according to the external information and type information.

[0086] Therefore, in the embodiment of the present disclosure, it is possible to receive the user's cloud disk operation request, then send the cloud disk operation request to the target cluster queue through the cluster management node, and finally send the cloud disk operation request to the target service node through the target cluster queue, so that the target service node processes the cloud disk operation request. Therefore, the cloud disk operation request can be sent to the target cluster queue through the cluster management node, and the target cluster queue sends the cloud disk operation request to the target service node for processing, so that the cloud disk operation request can be processed by the normal target service node to meet the user's operation needs.

[0087] In some embodiments of the present disclosure, the cloud disk operation request may include at least one of a deletion operation request, a capacity expansion operation request, and a snapshot operation request.

[0088] In some embodiments of the present disclosure, the cloud disk operation request processing device 300 may further include a first determination module and a second determination module.

[0089] The first determination module may be configured to determine a first target type to which the cloud disk operation request belongs after receiving a cloud disk operation request from a user.

[0090] The second determination module may be configured to determine a target cluster queue corresponding to the first target type from among multiple cluster queues.

[0091] In some embodiments of the present disclosure, the first target type may be used to characterize the type of the cluster queue.

[0092] In some embodiments of the present disclosure, the cloud disk operation request processing device 300 may further include a third determination module and a fourth determination module.

[0093] The third determination module may be configured to determine a second target type to which the cloud disk operation request belongs after the cloud disk operation request is sent to the target cluster queue through the cluster management node.

[0094] The fourth determination module may be used to determine a target service node corresponding to a second target type among a plurality of service nodes, where the second target type is used to characterize a type of the service node.

[0095] In some embodiments of the present disclosure, the second sending module 330 may also be specifically used to perform polling scheduling on multiple service sub-nodes included in the target service node based on a polling scheduling strategy, so that the service sub-nodes process the cloud disk operation request.

[0096] In some embodiments of the present disclosure, the cloud disk operation request processing device 300 may further include a polling scheduling module.

[0097] The polling scheduling module can be used to perform polling scheduling on the remaining service subnodes except the target service subnode among multiple service subnodes based on the polling scheduling strategy when a failure event occurs in the target service subnode among multiple service subnodes, so that the remaining service subnodes can process the cloud disk operation request.

[0098] It should be noted that Figure 3 The cloud disk operation request processing device 300 shown can execute Figure 1 to Figure 2 The various steps in the method embodiment shown in the figure are implemented Figure 1 to Figure 2The various processes and effects in the method embodiment shown are not described in detail here.

[0099] Figure 4 A schematic diagram of the structure of a cloud disk operation request processing device provided by an embodiment of the present disclosure is shown.

[0100] In some embodiments of the present disclosure, Figure 4 The cloud disk operation request processing device shown may be executed by a server, wherein the server may include but is not limited to servers such as a cloud server or a cloud server cluster.

[0101] like Figure 4 As shown, the cloud disk operation request processing device may include a processor 401 and a memory 402 storing computer program instructions.

[0102] Specifically, the processor 401 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

[0103] The memory 402 may include a large capacity memory for information or instructions. By way of example and not limitation, the memory 402 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a tape, or a universal serial bus (USB) drive or a combination of two or more of these. Where appropriate, the memory 402 may include a removable or non-removable (or fixed) medium. Where appropriate, the memory 402 may be inside or outside the integrated gateway device. In a particular embodiment, the memory 402 is a non-volatile solid-state memory. In a particular embodiment, the memory 402 includes a read-only memory (ROM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (Electrically Erasable Programmable ROM, EEPROM), an electrically rewritable ROM (EAROM) or a flash memory, or a combination of two or more of these.

[0104] The processor 401 reads and executes the computer program instructions stored in the memory 402 to perform the steps of the cloud disk operation request processing method provided in the embodiment of the present disclosure.

[0105] In one example, the cloud disk operation request processing device may further include a transceiver 403 and a bus 404. Figure 4 As shown, the processor 401, the memory 402 and the transceiver 403 are connected via a bus 404 and communicate with each other.

[0106] The bus 404 includes hardware, software, or both. For example, but not limitation, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industrial Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count (LPC) bus, a Memory bus, a MicroChannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses or a combination of two or more of these. Where appropriate, the bus 404 may include one or more buses. Although embodiments of the present application describe and illustrate a particular bus, the present application contemplates any suitable bus or interconnect.

[0107] The embodiment of the present disclosure further provides a computer-readable storage medium, which may store a computer program. When the computer program is executed by a processor, the processor implements the cloud disk operation request processing method provided by the embodiment of the present disclosure.

[0108] The above-mentioned storage medium may, for example, include a memory 402 of computer program instructions, and the above-mentioned instructions may be executed by the processor 401 of the cloud disk operation request processing device to complete the cloud disk operation request processing method provided by the embodiment of the present disclosure. Optionally, the storage medium may be a non-temporary computer-readable storage medium, for example, the non-temporary computer-readable storage medium may be a ROM, a random access memory (Random Access Memory, RAM), a compact disc read-only memory (Compact Disc ROM, CD-ROM), a magnetic tape, a floppy disk, and an optical data storage device, etc.

[0109] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the term "comprising" is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device.

[0110] The above description is only a specific embodiment of the present disclosure, so that those skilled in the art can understand or implement the present disclosure. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments described herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for processing a cloud disk operation request, characterized in that: include: Receive the user's cloud disk operation request; Sending the cloud disk operation request to the target cluster queue through the cluster management node; The cloud disk operation request is sent to a target service node through the target cluster queue, so that the target service node processes the cloud disk operation request.

2. The method according to claim 1, characterized in that: The cloud disk operation request includes at least one of a deletion operation request, a capacity expansion operation request, and a snapshot operation request.

3. The method according to claim 1, characterized in that After receiving the user's cloud disk operation request, the method further includes: Determine a first target type to which the cloud disk operation request belongs; The target cluster queue corresponding to the first target type is determined from a plurality of cluster queues.

4. The method according to claim 3, characterized in that The first target type is used to characterize the type of the cluster queue.

5. The method according to claim 1, characterized in that After sending the cloud disk operation request to the target cluster queue through the cluster management node, the method further includes: Determine a second target type to which the cloud disk operation request belongs; The target service node corresponding to the second target type is determined among a plurality of service nodes, where the second target type is used to characterize the type of the service node.

6. The method according to claim 1, characterized in that The enabling the target service node to process the cloud disk operation request includes: Based on the polling scheduling strategy, multiple service sub-nodes included in the target service node are polled and scheduled, so that the service sub-nodes process the cloud disk operation request.

7. The method according to claim 6, characterized in that The method further comprises: In the event of a failure event occurring in a target service subnode among the multiple service subnodes, based on a polling scheduling strategy, polling scheduling is performed on the remaining service subnodes among the multiple service subnodes except the target service subnode, so that the remaining service subnodes process the cloud disk operation request.

8. A cloud disk operation request processing device, characterized in that: include: A request receiving module, used to receive a user's cloud disk operation request; A first sending module, configured to send the cloud disk operation request to a target cluster queue through a cluster management node; The second sending module is used to send the cloud disk operation request to a target service node through the target cluster queue, so that the target service node processes the cloud disk operation request.

9. A cloud disk operation request processing device, characterized in that: include: processor; A memory for storing executable instructions; The processor is used to read the executable instructions from the memory and execute the executable instructions to implement the cloud disk operation request processing method described in any one of claims 1 to 7.

10. A non-volatile computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by the processor, the processor implements the cloud disk operation request processing method described in any one of claims 1 to 7.

Images