Overload control method and device in object storage service system

WO2024160207A9PCT designated stage expired Publication Date: 2024-12-05HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/074758
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-01-31
Filing Date
2024-01-30
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

When the object storage service system faces connection number attacks, it is difficult to effectively control the scope of the impact, resulting in the access of other tenants being affected. The existing technology requires manual intervention by managers and may affect business stability.

Method used

Bind multiple IP addresses to the service node of the object storage service system. Each IP address corresponds to one or more tenants. By receiving access requests and determining the number of TCP connections to the target IP address, the request is discarded when the number exceeds the preset threshold. , use the DPDK user-mode protocol stack for efficient overload control to avoid affecting other tenants.

Benefits of technology

Effectively reduce the scope of impact of connection number attacks, avoid affecting tenants in the entire cluster, reduce the impact on user businesses, and achieve adaptive overload control without the need for management personnel to participate.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024074758_05122024_PF_FP_ABST
    Figure CN2024074758_05122024_PF_FP_ABST
Patent Text Reader

Abstract

Embodiments of the present application relate to the technical field of object storage, and provide an overload control method and device in an object storage service system, which can effectively reduce the impact range of a connection flood attack and avoid affecting tenants of the entire cluster. The method is applied to a service node in an object storage service system, the service node is bound to a plurality of IP addresses, and each IP address in the plurality of IP addresses corresponds to one or more tenants. The method comprises: receiving an access request from a user equipment, wherein the access request is used for requesting to access a storage bucket of a target tenant, the access request comprises a target IP address, and the target IP address is one of the plurality of IP addresses; then determining the number of TCP connections corresponding to the target IP address in a TCP accept queue of the service node; and discarding the access request when the number of TCP connections corresponding to the target IP address is greater than a first preset threshold.
Need to check novelty before this filing date? Find Prior Art

Description

Overload control method and device in object storage service system

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on January 31, 2023, with application number 202310064237.5 and application name “Overload Control Method and Device in Object Storage Service System”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present invention relates to the field of object storage technology, and more particularly to an overload control method and apparatus in an object storage service system. Background Art

[0003] The object storage service (OBS) can provide massive, secure, highly reliable, and low-cost data storage capabilities. Tenants can purchase storage resources from the object storage service to store various types of data.

[0004] Typically, an object storage service system has nearly a million tenants, each corresponding to a single IP address. If a tenant receives too many access requests, and too many connections are established to transmit data in response to those requests, the tenant is considered to be experiencing a connection attack or overload. When a tenant in the object storage service system experiences a connection attack, it can also affect user access to data belonging to other tenants in the system.

[0005] Therefore, it is very important to control the number of connections (or overload control) for the object storage service system.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide an overload control method and device in an object storage service system, which can effectively reduce the impact range of connection number attacks and avoid affecting tenants of the entire cluster.

[0008] To achieve the above objectives, the present invention adopts the following technical solutions:

[0009] In a first aspect, an embodiment of the present application provides an overload control method in an object storage service system, which is applied to a service node in the object storage service system, wherein the service node is bound to multiple IP addresses, and each of the multiple IP addresses corresponds to one or more tenants. The method includes: receiving an access request from a user device, wherein the access request is used to request access to a storage bucket of a target tenant, and the access request includes a target IP address, which is one of multiple IP addresses; then, determining the number of TCP connections corresponding to the target IP address in the TCP full connection queue of the service node; and discarding the access request if the number of TCP connections corresponding to the target IP address is greater than a first preset threshold.

[0010] In an embodiment of the present application, since each of the multiple IP addresses bound to the service node corresponds to one or more tenants, when the number of connections corresponding to the target IP address is overloaded, the service node discards the access request of the tenant corresponding to the target IP address, and the service node processes the access requests corresponding to other IP addresses normally. In this way, the impact range of the connection number attack can be effectively reduced to avoid affecting the tenants of the entire cluster.

[0011] In one possible implementation, discarding an access request when the number of TCP connections corresponding to the target IP address is greater than a first preset threshold includes: based on a DPDK user-mode protocol stack, discarding the access request when the number of TCP connections corresponding to the target IP address is greater than the first preset threshold to alleviate connection overload. It is understood that DPDK is a software library for accelerating packet processing at the network protocol transport layer. DPDK has efficient processing capabilities, and a DPDK-based user-mode protocol stack can efficiently control connection overload.

[0012] When the number of TCP connections corresponding to the target IP address is greater than the first preset threshold, the service node only discards the current access request containing the target IP address, and the service node will not discard the access request containing other IP addresses. In this way, the service node will not affect the services corresponding to other tenants during the process of controlling the number of connections overload.

[0013] In one possible implementation, the overload control method in the object storage service system provided in an embodiment of the present application also includes: establishing a TCP connection between the user device and the service node when the number of TCP connections corresponding to the target IP address is less than or equal to a first preset threshold.

[0014] In this application, if the number of TCP connections corresponding to the target IP address is less than or equal to the first preset threshold, it means that the number of TCP connections corresponding to the target IP is not overloaded, and the service node enters the TCP connection establishment process to establish a TCP connection between the user device and the service node, and places the TCP connection in the TCP full connection queue maintained by the service node, waiting for the application layer to process the access request corresponding to the TCP connection.

[0015] In one possible implementation, after establishing a TCP connection between the user device and the service node, the overload control method provided in an embodiment of the present application also includes: determining whether the length of the access request queue corresponding to the target tenant's storage bucket is greater than a second preset threshold; if the length of the access request queue is greater than the second preset threshold, refusing to process the access request; if the length of the access request queue is less than or equal to the second preset threshold, processing the access request.

[0016] In this application, each tenant has an access request queue that includes all access requests for which a TCP connection has been established. After receiving the access request through the network transport protocol layer, the service node establishes the corresponding TCP connection and then processes the access request at the application layer.

[0017] For the target tenant, if the length of the access request queue corresponding to the storage bucket of the above-mentioned target tenant is greater than the second preset threshold, it means that the target tenant is overloaded. At this time, the service node refuses to process the access request; if the length of the access request queue is less than or equal to the second preset threshold, it means that the target tenant is not overloaded. At this time, the service node processes the access request to ensure the service quality of the tenant.

[0018] In one possible implementation, the first preset threshold is half the TCP full connection queue capacity. The first preset threshold can be determined based on the TCP full connection queue capacity (queue capacity can also be called queue depth), and the first preset threshold does not need to be adjusted according to the processing capacity of the application layer.

[0019] In a second aspect, an embodiment of the present application provides a service node that is bound to multiple IP addresses, each of which corresponds to one or more tenants. The service node includes a receiving module, a determining module, and a processing module. The receiving module is configured to receive an access request from a user device, the access request being for accessing a storage bucket of a target tenant, the access request including a target IP address, which is one of the multiple IP addresses; the determining module is configured to determine the number of TCP connections corresponding to the target IP address in a TCP full connection queue of the service node; and the processing module is configured to discard the access request if the number of TCP connections corresponding to the target IP address is greater than a first preset threshold.

[0020] In a possible implementation, the processing module is specifically configured to discard the access request based on a DPDK user-mode protocol stack when the number of TCP connections corresponding to the target IP address is greater than a first preset threshold.

[0021] In a possible implementation, the processing module is further configured to establish a TCP connection between the user equipment and the service node when the number of TCP connections corresponding to the target IP address is less than or equal to a first preset threshold.

[0022] In one possible implementation, the above-mentioned determination module is also used to determine whether the length of the access request queue corresponding to the target tenant's storage bucket is greater than a second preset threshold; the processing module is also used to refuse to process the access request if the length of the access request queue is greater than the second preset threshold; and process the access request if the length of the access request queue is less than or equal to the second preset threshold.

[0023] In a possible implementation, the first preset threshold is half of the TCP full connection queue capacity.

[0024] In a third aspect, an embodiment of the present application provides a service node, comprising a memory and at least one processor connected to the memory, the memory being used to store computer program code, the computer program code comprising computer instructions, which, when executed by at least one processor, enable the computing device to execute the method described in the first aspect and any one of its possible implementations.

[0025] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium storing computer instructions, which, when executed on a computer, execute the method described in the first aspect and any one of its possible implementations.

[0026] In a fifth aspect, an embodiment of the present application provides a computer program product, which includes computer instructions. When the computer instructions are run on a computer, the method described in the first aspect and any one of its possible implementation methods is executed.

[0027] In a sixth aspect, an embodiment of the present application provides a chip comprising a memory and a processor, wherein the memory is used to store computer instructions, and the processor is used to call and run the computer instructions from the memory to execute the method described in the first aspect and any one of its possible implementation methods.

[0028] It should be understood that the beneficial effects achieved by the technical solutions of the second to sixth aspects of this application and the corresponding possible implementation methods can be referred to the technical effects of the first aspect and its corresponding possible implementation methods mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] FIG1 is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0030] FIG2 is a schematic diagram of the hardware structure of a service node provided in an embodiment of the present application;

[0031] FIG3 is a schematic diagram of the correspondence between tenants and IP addresses in an object storage service system provided in an embodiment of the present application;

[0032] FIG4 is a schematic diagram of an overload control method in an object storage service system according to an embodiment of the present application;

[0033] FIG5 is a second schematic diagram of an overload control method in an object storage service system provided by an embodiment of the present application;

[0034] FIG6 is a schematic diagram of a structure of a service node according to an embodiment of the present application;

[0035] FIG7 is a second structural diagram of a service node provided in an embodiment of the present application. DETAILED DESCRIPTION

[0036] The term "and / or" in this article is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0037] The terms "first" and "second" and the like in the description and claims of the embodiments of the present application are used to distinguish different objects rather than to describe a specific order of objects.

[0038] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0039] In the description of the embodiments of the present application, unless otherwise specified, “plurality” means two or more.

[0040] First, some concepts involved in the overload control method and device in the object storage service system provided in the embodiments of the present application are explained.

[0041] 1. Some concepts about Object Storage Service (OBS)

[0042] The basic components of the object storage service OBS are buckets and objects.

[0043] A bucket is a container for storing objects in OBS. Each bucket has attributes such as storage category, access permissions, and region.

[0044] An object is the basic unit of data storage in OBS. An object contains a file's data and its related attribute information, including key, metadata, and data. Key is the object's name; metadata is the object's description, including system metadata and user metadata; and data is the file's data content.

[0045] 2. Tenants of Object Storage Service

[0046] Users who rent OBS resources are called tenants of the object storage service. Tenants can create buckets in OBS, configure bucket access policies, and more through the OBS configuration interface or application programming interface (API). Tenants can then upload objects to buckets over the internet. Optionally, tenants can create one or more buckets.

[0047] After a tenant uploads an object to their bucket, other users (through their user devices) can access the tenant's bucket. Specifically, the user device can locate the bucket using the bucket's access domain name and access the objects in the bucket.

[0048] In the embodiment of the present application, tenants refer to the owners of buckets in OBS, and users refer to the visitors of the tenants' buckets.

[0049] The following describes the architecture of a communication system for an object storage service in conjunction with Figure 1. As shown in Figure 1, the communication system includes a user device 101 (such as a mobile phone), a border router (BR) 102, and an OBS system 103. The OBS system 103 may include multiple clusters (only one cluster is illustrated in Figure 1). A cluster includes multiple service nodes, which are responsible for creating and managing buckets.

[0050] The user has a user device 101 , which can access the service node in the OBS system 103 through the Internet and the border router 102 , and obtain objects from the bucket created by the service node.

[0051] As shown in Figure 1, a cluster in OBS system 103 presents a single virtual IP address to the outside world. Typically, one IP address hosts nearly one million tenants. In other words, all tenants of buckets on multiple service nodes in OBS system 103 correspond to one IP address.

[0052] For a tenant, a user sends an access request through a user device to access objects in the tenant's bucket. After receiving the access request, the service node establishes a communication connection (e.g., a Transmission Control Protocol (TCP) connection) between the user device and the service node. Subsequently, the user device can communicate with the service node to transmit data. In some cases, a large number of users may access the tenant's bucket. When a tenant receives too many access requests, the number of connections established for data transmission in response to these requests also increases. In this case, the tenant is considered to be under a connection attack or overloaded.

[0053] Because all tenants in a cluster present the same IP address to the outside world, when a tenant is attacked by a connection attack, it will affect the access of all tenants in the entire cluster, that is, it will affect other users' access to other tenants in the cluster.

[0054] Currently, one solution for handling connection count attacks is for administrators to log in to the service node and use iptables to block access requests from certain user devices. It should be understood that iptables is a firewall, and the service node uses iptables in kernel mode to block source IP addresses (the source IP address is the IP address of the user device). For more details on using iptables to block access requests from user devices, please refer to existing technical documents and will not be described in detail in this embodiment.

[0055] In the above solution of handling connection number attacks using iptable technology, since the tenant has already been attacked by connection number attacks, the service node's processing efficiency is very low. At this time, the administrator may face the problem of being unable to log in to the service node, and therefore, it is impossible to handle the connection number attacks in a timely and effective manner.

[0056] Another solution to handle connection-count attacks is to block source IP addresses at the border router. This solution has the risk of blocking too many source IP addresses. For example, legitimate user access requests may be blocked, severely impacting services and putting users' businesses at risk.

[0057] In response to the above problems, an embodiment of the present application provides an overload control method and device in an object storage service system. The method is applied to a service node in the object storage service system, and the service node is bound to multiple IP addresses, each of the multiple IP addresses corresponds to one or more tenants. The overload control method includes: the service node receives an access request from a user device, and the access request is used to request access to the storage bucket of the target tenant, and the access request includes a target IP address, and the target IP address is one of the above multiple IP addresses; then, the service node determines the number of TCP connections corresponding to the target IP address in the TCP full connection queue of the service node; and, when the number of TCP connections corresponding to the target IP address is greater than a first preset threshold, the access request of the user device is discarded. The technical solution provided by the embodiment of the present application can effectively reduce the impact range of the connection number attack and avoid affecting the tenants of the entire cluster.

[0058] In addition, compared to the above-mentioned method of overload control by administrators logging into the service node, the technical solution provided by the embodiment of the present application does not require the participation of administrators and can adaptively perform overload control. Compared to the above-mentioned solution of overload control through the border router, the technical solution provided by the embodiment of the present application controls the number of TCP connections corresponding to the tenant's IP address (which is the destination IP address), and no longer controls the number of connections by blocking the source IP address (the user's IP address), thereby reducing the impact on the user's business.

[0059] In the embodiments of the present application, the device that executes the above-mentioned overload control method is a service node of the OBS system shown in Figure 1. The scheduler can be a device such as a desktop computer, a portable computer, or a personal digital assistant (PDA). The service node can also be one or more functional modules within the device. The functional modules can be components within a hardware device, software running on dedicated hardware, or a combination of hardware and software. Optionally, the service node can be implemented by a single device or multiple devices, which is not specifically limited in the embodiments of the present application.

[0060] Please refer to Figure 2 for an introduction to the hardware structure of the service node provided in this application. The various components shown in Figure 2 can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits. As shown in Figure 2, the service node may include: a processor 201, a memory 202, and a communication interface 203. The processor 201, the memory 202, and the communication interface 203 may be connected to each other via a bus 204, or by other means.

[0061] The processor 201 is the control center of the service node. The processor 201 may be a general-purpose central processing unit (CPU) or other general-purpose processor. The general-purpose processor may be a microprocessor or any conventional processor. For example, the processor 201 may include an application processor (AP), a graphics processing unit (GPU), an image signal processor (ISP), a controller, etc.

[0062] The controller in processor 201 is the nerve center and command center of the service node. Based on instruction opcodes and timing signals, the controller generates operational control signals to control instruction fetching and execution. Optionally, processor 201 may also include a memory for storing instructions and data. Exemplarily, processor 201 may include one or more CPUs, such as CPU 0 and CPU 1 shown in Figure 2.

[0063] The memory 202 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical storage, magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer. In the embodiment of the present application, the memory 202 can store information such as computer instructions.

[0064] In one possible implementation, memory 202 can exist independently of processor 201. Memory 202 can be connected to processor 201 via bus 204 and is used to store data, instructions, or program code. When processor 201 calls and executes the instructions or program code stored in memory 202, the overload control method in the object storage service system provided in the embodiment of the present application can be implemented.

[0065] In another possible implementation, the memory 202 may also be integrated with the processor 201 .

[0066] The communication interface 203 may be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, or wireless local area networks (WLAN). The communication interface 203 may receive instructions, messages, or data. The transceiver module may be a device such as a transceiver or a transceiver. Alternatively, the communication interface 203 may be a transceiver circuit located within the processor 201, for implementing signal input and output of the processor. The communication interface 203 may be a wired interface (port), such as a fiber distributed data interface (FDDI) or a gigabit Ethernet (GE) interface, or the communication interface 203 may be a wireless interface.

[0067] Bus 204 may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. This bus can be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, FIG2 shows only one thick line, but this does not mean that there is only one bus or only one type of bus.

[0068] It should be noted that the service node shown in FIG2 is merely an example of a service node, and the service node may have more or fewer components than those shown in FIG2 , may combine two or more components, or may have different component configurations.

[0069] The following describes the overload control method in the object storage service system provided by the embodiment of the present application with reference to the accompanying drawings. The method is applied to a service node in the object storage service system, and the service node is bound to multiple IP addresses (the multiple IP addresses are virtual IP addresses), and each of the multiple IP addresses corresponds to one or more tenants. In the embodiment of the present application, the OBS system presents multiple IP addresses to the outside world, and the multiple IP addresses are mounted on a single service node, that is, a service node is bound to multiple IP addresses. Moreover, each of the multiple IP addresses corresponds to one or more tenants, that is, multiple tenants are hashed on different IP addresses. For example, tenant 1 and tenant 2 in Figure 3 correspond to IP address 1, tenant 3 and tenant 4 correspond to IP address 2, ..., tenant 199 and tenant 200 correspond to IP address 100.

[0070] As shown in FIG4 , the overload control method in the object storage service system provided in an embodiment of the present application may include the following steps:

[0071] S301: Receive an access request from a user device, where the access request includes a target IP address.

[0072] The above access request is used to request access to the target tenant's bucket (the bucket is a bucket created by the target tenant and contains objects). The target IP address in the access request is one of the multiple IP addresses bound to the service node.

[0073] It should be understood that the specific process of the service node receiving the access request from the user equipment includes S1-S3:

[0074] S1. The user device sends an access request to the domain name server. The access request includes the domain name of the target tenant's bucket.

[0075] A bucket's domain name can be written as bucket1.region1.com, where bucket1 is the bucket's identifier and region1 represents the region where the bucket is located. Bucket domain names are unique, and each bucket corresponds to a tenant. Therefore, bucket domain names also have tenant attributes.

[0076] S2. The domain name server sends the target IP address to the user device based on the domain name of the target tenant's bucket.

[0077] The domain name server stores the mapping between bucket identifiers and IP addresses. Based on the domain name of the target tenant's bucket in the access request, the domain name server determines the target IP address corresponding to the bucket and returns the target IP address to the user device. As you can see, the bucket in the OBS system can be accessed based on the target IP address.

[0078] S3. The user equipment sends an access request including the target IP address to the service node. Correspondingly, the service node receives the access request from the user equipment.

[0079] S302: Determine the number of TCP connections corresponding to the target IP address in the TCP full connection queue of the service node.

[0080] It is understandable that, generally, after the service node receives the access request from the user device, at the network transmission protocol layer, the service node enters the TCP connection establishment process, for example, establishing a TCP connection with the user device through a three-way handshake process. For the TCP connection establishment process, reference can be made to the prior art. After the service node completes the TCP connection establishment process, the service node places the TCP connection into a TCP full connection queue maintained by the service node, and then the service node processes (or consumes) the access request corresponding to the TCP connection in the TCP full connection queue at the application layer. In an embodiment of the present application, after the service node receives the access request from the user device, the service node does not directly enter the TCP connection establishment process, but first determines the number of TCP connections corresponding to the target IP address in the TCP full connection queue in the service node based on the target IP address in the access request, and determines whether a connection number attack has occurred based on the number of TCP connections.

[0081] S303: If the number of TCP connections corresponding to the target IP address is greater than a first preset threshold, discard the access request.

[0082] The above-mentioned service node controls the number of connections corresponding to the target IP address at the network protocol transport layer. If the number of TCP connections corresponding to the target IP address is greater than a first preset threshold, it indicates that the number of TCP connections corresponding to the target IP is overloaded, and the service node discards the access request (also known as rejecting the access request) to alleviate the connection overload. For example, in conjunction with Figure 4 above, assuming that the target IP address is IP address 1, and IP address 1 corresponds to tenant 1 and tenant 2, if the number of TCP connections corresponding to IP address 1 is overloaded, it indicates that tenant 1 and / or tenant 2 are under a connection attack.

[0083] The first preset threshold can be determined based on the TCP full connection queue capacity (queue capacity may also be referred to as queue depth). This first preset threshold does not need to be adjusted based on the processing power of the application layer. Optionally, the TCP full connection queue capacity refers to the maximum number of TCP connections that the TCP full connection queue can accommodate. Optionally, the first preset threshold is half of the TCP full connection queue capacity. For example, if the TCP full connection queue capacity is 60,000, the first preset threshold is 30,000.

[0084] In one implementation, the above S303 is specifically implemented through S3031.

[0085] S3031. Based on a user-mode protocol stack of an Intel Data Plane Development Kit (DPDK), if the number of TCP connections corresponding to the target IP address is greater than a first preset threshold, discard the access request.

[0086] As you can understand, DPDK is a software library used to accelerate packet processing. DPDK has efficient processing capabilities, and the user-mode protocol stack based on DPDK can efficiently control connection overload.

[0087] S304: When the number of TCP connections corresponding to the target IP address is less than or equal to a first preset threshold, establish a TCP connection between the user equipment and the service node.

[0088] In an embodiment of the present application, if the number of TCP connections corresponding to the target IP address is less than or equal to a first preset threshold, it indicates that the number of TCP connections corresponding to the target IP is not overloaded, and the service node enters the TCP connection establishment process to establish a TCP connection between the user device and the service node, and places the TCP connection in the TCP full connection queue maintained by the service node, waiting for the application layer to process the access request corresponding to the TCP connection. For example, in conjunction with Figure 4 above, assuming that the target IP address is IP address 2, and IP address 2 corresponds to tenants 3 and 4, if the number of TCP connections corresponding to IP address 2 is not overloaded, it indicates that tenants 3 and 4 are not under connection number attack, and the service node can process the access requests of tenants 3 and 4 normally.

[0089] In summary, when the number of TCP connections corresponding to the target IP address is greater than the first preset threshold, the service node only discards the current access request containing the target IP address, and the service node will not discard the access request containing other IP addresses. In this way, the service node will not affect the services corresponding to other tenants during the process of controlling the number of connections overload. For example, referring to Figure 4, if the target IP address is IP address 1, when the number of TCP connections corresponding to IP address 1 is greater than the first preset threshold, the service node discards the access request for the storage bucket of tenant 1 and / or tenant 2, and the service node normally processes the access request for accessing the storage bucket of other tenants. For example, the service node will normally process the service requests of tenants 3 to tenant 200. That is, in the process of controlling the number of TCP connections overload, the service node minimizes the impact range of the connection attack to the greatest extent, avoids affecting the tenants of the entire cluster, and prevents tenants from interfering with each other.

[0090] In conjunction with FIG4 , as shown in FIG5 , after establishing the TCP connection between the user device and the service node, the overload control method in the object storage service system provided by the embodiment of the present application further includes:

[0091] S305: Determine whether the length of the access request queue corresponding to the target tenant's storage bucket is greater than a second preset threshold.

[0092] S306: When the length of the access request queue is greater than a second preset threshold, refuse to process the access request.

[0093] S307: When the length of the access request queue is less than or equal to the second preset threshold, process the access request.

[0094] It should be noted that the above S305-S307 are actions performed by the service node at the application layer.

[0095] In this embodiment of the present application, each tenant has an access request queue corresponding to it. This access request queue includes all access requests for which a TCP connection has been established. After being processed by the network transport protocol layer, the service node receives the access request, establishes the corresponding TCP connection, and then processes the access request at the application layer.

[0096] For the target tenant, if the length of the access request queue corresponding to the storage bucket of the above-mentioned target tenant is greater than the second preset threshold, it means that the target tenant is overloaded. At this time, the service node refuses to process the access request; if the length of the access request queue is less than or equal to the second preset threshold, it means that the target tenant is not overloaded. At this time, the service node processes the access request to ensure the service quality of the tenant.

[0097] Based on the above, the overload control method in the object storage system provided by the embodiment of the present application is that the service node receives an access request including a target IP address from a user device, the access request is used to request access to the storage bucket of the target tenant, the service node is bound to multiple IP addresses, each of the multiple IP addresses corresponds to one or more tenants, and the above target IP address is one of the above multiple IP addresses; then, the service node determines the number of TCP connections corresponding to the target IP address in the TCP full connection queue of the service node; and, when the number of TCP connections corresponding to the target IP address is greater than a first preset threshold, the access request of the user device is discarded. Since each of the multiple IP addresses bound to the service node corresponds to one or more tenants, when the number of connections corresponding to the target IP address is overloaded, the service node discards the access request of the tenant corresponding to the target IP address, and the service node normally processes the access requests corresponding to other IP addresses. In this way, the impact range of the connection number attack can be effectively reduced to avoid affecting tenants of the entire cluster.

[0098] Accordingly, an embodiment of the present application provides a service node. In an embodiment of the present application, the service node can be divided into functional modules according to the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0099] In the case of dividing each functional module according to its function, Figure 6 shows a possible structural diagram of the service node involved in the above embodiment. The service node is bound to multiple IP addresses, each of which corresponds to one or more tenants. As shown in Figure 6, the service node includes a receiving module 601, a determining module 602, and a processing module 603. The receiving module 601 is configured to receive an access request from a user device, wherein the access request is for accessing a storage bucket of a target tenant, and the access request includes a target IP address, which is one of the multiple IP addresses, such as executing S301 in the above method embodiment. The determining module 602 is configured to determine the number of TCP connections corresponding to the target IP address in the service node's TCP full connection queue, such as executing S302 in the above method embodiment. The processing module 603 is configured to discard the access request if the number of TCP connections corresponding to the target IP address exceeds a first preset threshold, such as executing S303 in the above method embodiment.

[0100] Optionally, the processing module 603 is specifically used to discard the access request based on the DPDK user-mode protocol stack when the number of TCP connections corresponding to the target IP address is greater than a first preset threshold, such as executing S3031 in the above method embodiment. The processing module 603 is also used to establish a TCP connection between the user device and the service node when the number of TCP connections corresponding to the target IP address is less than or equal to the first preset threshold, such as executing S304 in the above method embodiment. The determination module 602 is also used to determine whether the length of the access request queue corresponding to the target tenant's storage bucket is greater than a second preset threshold, such as executing S305 in the above method embodiment; the processing module 603 is also used to refuse to process the access request when the length of the access request queue is greater than the second preset threshold, and to process the access request when the length of the access request queue is less than or equal to the second preset threshold, such as executing S306-S307 in the above method embodiment.

[0101] Each module of the above service node can also be used to perform other actions in the above method embodiment. All relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0102] In the case of adopting an integrated unit, Figure 7 shows another possible structural diagram of the service node involved in the above embodiment. As shown in Figure 7, the service node provided in the embodiment of the present application may include: a processing module 701 and a communication module 702. The processing module 701 can be used to control and manage the actions of the service node. For example, the processing module 701 can be used to support the service node to execute S302, S303 (including S3031), S304-S307 in the above method embodiment, and / or other processes for the technology described herein. The communication module 702 can be used to support the communication between the service node and other network entities, for example, to support the communication between the service node and the computing node. For example, the communication module 702 can be used to support the service node to execute S301 in the above method embodiment. Optionally, as shown in Figure 7, the service node may also include a storage module 703 for storing computer instructions and data.

[0103] Among them, the processing module 701 can be a processor or a controller (for example, it can be the processor 201 shown in Figure 2 above). The above-mentioned processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc. The communication module 702 can be a communication interface (for example, it can be the communication interface 203 shown in Figure 2 above). The storage module 703 can be a memory (for example, it can be the memory 202 shown in Figure 2 above). When the processing module 701 is a processor, the communication module 702 is a communication interface, and the storage module 703 is a memory, the processor, transceiver, and memory can be connected via a bus.

[0104] For more details on how the modules included in the service node implement the above functions, please refer to the descriptions in the previous method embodiments, which will not be repeated here. The various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referenced to each other. Each embodiment focuses on the differences from other embodiments.

[0105] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions in accordance with the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a magnetic disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state drive (SSD)).

[0106] Through the description of the above embodiments, those skilled in the art will clearly understand that for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working processes of the above-described systems, devices, and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0107] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0108] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0109] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0110] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk.

[0111] The above is only a specific embodiment of the present application, but the scope of protection of this application is not limited to this. Any changes or substitutions within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for overload control in an object storage service system, characterized in that: A method for applying a service node in an object storage service system to a plurality of IP addresses, wherein each of the plurality of IP addresses corresponds to one or more tenants, comprising: Receive an access request from a user device; wherein the access request is used to request access to a storage bucket of a target tenant, and the access request includes a target IP address, which is one of the multiple IP addresses; Determining the number of TCP connections corresponding to the target IP address in a Transmission Control Protocol (TCP) full connection queue of the service node; If the number of TCP connections corresponding to the target IP address is greater than a first preset threshold, the access request is discarded.

2. The method according to claim 1, characterized in that The discarding of the access request when the number of TCP connections corresponding to the target IP address is greater than a first preset threshold includes: Based on the user-mode protocol stack of the data plane development kit DPDK, when the number of TCP connections corresponding to the target IP address is greater than the first preset threshold, the access request is discarded.

3. The method according to claim 1 or 2, characterized in that The method further comprises: When the number of TCP connections corresponding to the target IP address is less than or equal to the first preset threshold, a TCP connection is established between the user equipment and the service node.

4. The method according to claim 3, characterized in that After establishing the TCP connection between the user equipment and the service node, the method further includes: Determining whether the length of the access request queue corresponding to the target tenant's storage bucket is greater than a second preset threshold; If the length of the access request queue is greater than the second preset threshold, refusing to process the access request; When the length of the access request queue is less than or equal to the second preset threshold, the access request is processed.

5. The method according to any one of claims 1 to 4, characterized in that The first preset threshold is half of the TCP full connection queue capacity.

6. A service node, characterized in that: The service node is bound to multiple IP addresses, each of the multiple IP addresses corresponds to one or more tenants, and the service node includes a receiving module, a determining module, and a processing module; The receiving module is configured to receive an access request from a user device; wherein the access request is used to request access to a storage bucket of a target tenant, and the access request includes a target IP address, which is one of the multiple IP addresses; The determining module is configured to determine the number of TCP connections corresponding to the target IP address in the Transmission Control Protocol TCP full connection queue of the service node; The processing module is configured to discard the access request when the number of TCP connections corresponding to the target IP address is greater than a first preset threshold.

7. The service node according to claim 6, wherein: The processing module is specifically configured to discard the access request based on the user-mode protocol stack of the data plane development kit DPDK when the number of TCP connections corresponding to the target IP address is greater than the first preset threshold.

8. The service node according to claim 6 or 7, characterized in that: The processing module is further configured to establish a TCP connection between the user equipment and the service node when the number of TCP connections corresponding to the target IP address is less than or equal to the first preset threshold.

9. The service node according to claim 8, wherein: The determining module is further configured to determine whether the length of the access request queue corresponding to the storage bucket of the target tenant is greater than a second preset threshold; The processing module is further configured to refuse to process the access request if the length of the access request queue is greater than the second preset threshold; and to process the access request if the length of the access request queue is less than or equal to the second preset threshold.

10. The service node according to any one of claims 6 to 9, characterized in that: The first preset threshold is half of the TCP full connection queue capacity.

11. A service node, characterized in that: The method comprises a memory and at least one processor connected to the memory, wherein the memory is used to store computer program code, and the computer program code comprises computer instructions. When the computer instructions are executed by the at least one processor, the computing device executes the method according to any one of claims 1 to 5.

12. A computer-readable storage medium, characterized in that Computer instructions are stored, and when the computer instructions are run on a computer, the method according to any one of claims 1 to 5 is executed.