Method for sharing floating IP resources based on load balancing and related products

Abstract

The invention provides a method for sharing floating IP resources based on load balancing and related products, and the method comprises the steps: constructing a cloud native load balancing cluster, and configuring a floating virtual IP and a virtual port for the cluster; the flow of the client requesting the virtual IP is introduced into the current active load balancing node in the load balancing cluster; the seven-layer load balancing cluster is used as a back-end server to be cascaded with the four-layer load balancing cluster, traffic analysis is carried out according to port quintuple information, and Hash scheduling is carried out; and according to an internal scheduling algorithm, a request is distributed to a back-end service server, and after the back-end service server processes the request, response data is returned to the client through the seven-layer load balancing cluster and the four-layer load balancing cluster in an original way. According to the method and the device, the service configuration and management process is simplified, so that the requirements of Internet services on high performance, high reliability and economical efficiency are better met, and the user experience is effectively improved.

Description

Technical Field

[0001] The present application belongs to the field of cloud computing technology, and in particular, relates to a method and related products for sharing floating IP resources based on load balancing. Background Art

[0002] With the rapid growth of Internet traffic and data, various businesses need to continuously improve their service capabilities. On the one hand, the configuration of a single server can be optimized, but hardware configuration has an upper limit and is expensive; on the other hand, multiple low-configuration servers can be used to build a cluster to provide services at the same time. This technology has become an IT standard due to its high availability and high economy. In the process of cluster construction, the most important technology is LB (Load Balance) technology. LB first receives the service request and then distributes the request to multiple back-end business servers RS (Real Server) according to the forwarding strategy.

[0003] Currently, LB technology can be divided into four-layer LB and seven-layer LB according to the level of the loaded business in OSI (Open System Interconnect). Four-layer LB works at the transport layer. LB distinguishes based on the source IP, source port, destination IP and destination port of the request, and then performs scheduling based on polling, weighting and other strategies; seven-layer LB works at the application layer. On the basis of distinguishing IP and port, it can also perform further scheduling based on service characteristics such as Url, Cookie, Host and other service characteristics of the request.

[0004] Traditional four-layer LB and seven-layer LB usually need to configure independent VIP (virtual IP) to provide services, which results in the need to occupy multiple IP addresses in the multi-level load balancing architecture, especially when providing multiple services, the consumption of IP resources increases rapidly. LBs in different services or different levels need to manually configure and manage multiple VIPs, which increases the complexity of operation and maintenance and the possibility of errors.

[0005] If the four-layer LB and the seven-layer LB use independent VIPs, when one of the LB nodes where the VIP is located fails, manual intervention or a complex failover mechanism may be required to restore the service. In traditional solutions, there is also a delay in the VIP switching process, which affects service continuity and user experience. Summary of the invention

[0006] In view of this, the present application aims to propose a method and related products for sharing floating IP resources based on load balancing to solve at least one of the above problems.

[0007] To achieve the above purpose, the technical solution of this application is implemented as follows:

[0008] In a first aspect, the present application provides a method for sharing floating IP resources based on load balancing, comprising:

[0009] Build a cloud-native load balancing cluster and configure a floating virtual IP and a virtual port for the cluster, wherein the cluster consists of multiple LB servers;

[0010] The client's request virtual IP traffic is introduced to the currently active load balancing node in the load balancing cluster through the network device;

[0011] The seven-layer load balancing cluster is used as a backend server and cascaded with the four-layer load balancing cluster. The four-layer load balancing cluster performs traffic analysis based on the port five-tuple information and performs five-tuple hash scheduling of the four-layer load balancing cluster so that the same five-tuple request is always routed to the same seven-layer load balancing instance.

[0012] The seven-layer load balancing cluster distributes the request to the backend business server according to its internal scheduling algorithm. After the backend business server processes the request, it returns the response data to the client through the seven-layer load balancing cluster and the four-layer load balancing cluster.

[0013] In a second aspect, based on the same inventive concept, the present application also provides a system for implementing a method for sharing floating IP resources based on load balancing, including:

[0014] A cluster building module is configured to build a cloud native load balancing cluster and configure a floating virtual IP and a virtual port for the cluster, wherein the cluster is composed of multiple LB servers;

[0015] The data request module is configured to introduce the traffic of the client requesting the virtual IP to the currently active load balancing node in the load balancing cluster through the network device;

[0016] The cascade module is configured to cascade the seven-layer load balancing cluster as a backend server with the four-layer load balancing cluster. The four-layer load balancing cluster performs traffic parsing according to the port five-tuple information, and performs five-tuple hash scheduling of the four-layer load balancing cluster so that the same five-tuple request is always routed to the same seven-layer load balancing instance.

[0017] The request processing module is configured as a seven-layer load balancing cluster to distribute requests to the backend business server according to its internal scheduling algorithm. After the backend business server processes the request, it returns the response data to the client through the seven-layer load balancing cluster and the four-layer load balancing cluster.

[0018] In a third aspect, based on the same inventive concept, the present application also provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the method described in the first aspect is implemented.

[0019] In a fourth aspect, based on the same inventive concept, the present application also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the method described in the first aspect.

[0020] Compared with the prior art, the method and related products for sharing floating IP resources based on load balancing described in this application have the following beneficial effects:

[0021] The method and related products of sharing floating IP resources based on load balancing described in the present application not only save IP resources and reduce costs by sharing floating IPs and optimizing traffic scheduling, but also improve the high availability and scalability of the system, simplify service configuration and management processes, thereby better meeting the Internet business's requirements for high performance, high reliability and economy, and effectively improving user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The drawings constituting a part of the present application are used to provide a further understanding of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0023] Figure 1 A flow chart of a method for sharing floating IP resources based on load balancing according to an embodiment of the present application;

[0024] Figure 2 A schematic diagram of a specific implementation of the method for sharing floating IP resources based on load balancing described in an embodiment of the present application;

[0025] Figure 3 A schematic diagram of the system structure based on load balancing and sharing floating IP resources according to an embodiment of the present application;

[0026] Figure 4 This is a schematic diagram of the hardware structure of the electronic device described in the embodiment of the present application. DETAILED DESCRIPTION

[0027] In order to make the objectives, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0028] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present application should be the usual meanings understood by people with ordinary skills in the field to which the present application belongs. The "first", "second" and similar words used in the embodiments of the present application do not represent any order, quantity or importance, but are only used to distinguish different components. "Including" or "comprising" and similar words mean that the elements or objects appearing in front of the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0029] Based on the above background technology, this application is based on software LB, draws on the DR (Direct Route) forwarding mode of LVS (Linux Virtual Server), cascades the four-layer LB and the seven-layer LB, so that a floating IP can be shared by the four-layer LB and the seven-layer LB cluster, and different services are provided using the same IP but different ports. In this way, the purpose of saving IP resources is achieved. Customers only need one IP to access the four-layer LB and the seven-layer LB, and it is also convenient for customers to configure and schedule domain names for services.

[0030] In order to achieve the purpose of sharing floating IP addresses, the present invention deploys software LB clusters in a cloud-native manner, and applications that call four-layer LB and seven-layer LB only need to configure an IP or domain name, which includes cluster management, traffic scheduling, port management, health check, etc. The following describes the embodiments of the present application in detail with reference to the accompanying drawings.

[0031] See also Figure 1 As shown, this embodiment provides a method for sharing floating IP resources based on load balancing, which specifically includes the following steps:

[0032] Step S101: Build a cloud native load balancing cluster and configure a floating virtual IP and a virtual port for the cluster, wherein the cluster consists of multiple LB servers.

[0033] Step S102: introducing the traffic of the client requesting the virtual IP to the currently active load balancing node in the load balancing cluster through the network device.

[0034] Step S103: The seven-layer load balancing cluster is cascaded with the four-layer load balancing cluster as a backend server. The four-layer load balancing cluster performs traffic parsing according to the port five-tuple information, and performs five-tuple hash scheduling of the four-layer load balancing cluster so that the same five-tuple request is always routed to the same seven-layer load balancing instance.

[0035] Step S104: The seven-layer load balancing cluster distributes the request to the backend business server according to its internal scheduling algorithm. After the backend business server processes the request, it returns the response data to the client through the seven-layer load balancing cluster and the four-layer load balancing cluster.

[0036] Specifically, in this embodiment, an LB cluster is composed of multiple LB servers (general Linux servers or cloud virtual machines), which provide services to the outside world through a floating VIP and VPORT. The traffic of the client requesting VIP is directed by the network device to the server carrying the floating VIP in the LB cluster. The server is then dispatched to a healthy business server according to the hash scheduling algorithm, and returns to the client after obtaining a response.

[0037] In this embodiment, the DR forwarding mode of LVS is used for reference, and the seven-layer LB cluster is cascaded with the four-layer LB cluster as the back-end server. The four-layer LB uses a hash scheduling algorithm to calculate a fixed scheduling result based on the five-tuple information of source IP, source port, protocol number, destination IP and destination port. That is, the same five-tuple can be fixedly scheduled to the same seven-layer LB instance through different four-layer LB instances, supporting multi-active; at the same time, in order to enable the back-end business RS to obtain the real client source IP, the four-layer LB needs to pass the client source IP address to the seven-layer LB, and the seven-layer LB then passes it to the RS through the HTTP header field.

[0038] It should be noted that the hash scheduling algorithm described in this embodiment is a conventional hash value calculation method in the field. In addition to the hash scheduling algorithm adopted in this embodiment, a weighted polling scheduling algorithm can also be adopted. This embodiment does not make any technical improvements to the above-mentioned algorithm itself, so it will not be further elaborated.

[0039] In some implementations, port resources are dynamically allocated through automated tools, port usage is monitored in real time, and port allocation is dynamically adjusted based on traffic load and business needs.

[0040] Specifically, in this embodiment, port resources also need to be managed and allocated. Different service instances cannot use the same floating VIP+VPORT. According to the TCP / UDP protocol, one IP can support 65535 ports, that is, one floating IP can provide 65535 services. Port numbers can be freely allocated in the four-layer LB or seven-layer LB as long as there is no conflict.

[0041] It should be noted that the introduction of automated tools (such as Ansible and Terraform) can realize dynamic allocation and management of ports, reduce errors and conflicts in manual configuration, monitor port usage in real time, dynamically adjust port allocation according to traffic load and business needs, and ensure efficient use of resources.

[0042] In some implementations, the method further includes: regularly performing health checks on the load balancing cluster nodes and backend business servers by combining active detection and passive monitoring to detect whether they are in an available state.

[0043] Specifically, in this embodiment, health checks are performed on the LB nodes regularly to ensure that each node is operating normally; and health monitoring is performed on the backend RS to detect whether it is in an available state.

[0044] The accuracy of health checks is improved by combining active detection (this embodiment uses a method of regularly sending heartbeat requests) and passive monitoring (this embodiment uses a method of monitoring error rate and response time).

[0045] The method described in this embodiment not only saves IP resources and reduces costs by sharing floating IPs and optimizing traffic scheduling, but also improves the high availability and scalability of the system, simplifies service configuration and management processes, thereby better meeting the Internet business requirements for high performance, high reliability and economy, and effectively improving user experience.

[0046] Based on the above method, the following specific embodiments are provided:

[0047] Reference Figure 2 , through DR mode cascading, the configuration process is as follows:

[0048] 1. Create a 4LB instance 4lb1 normally:

[0049] a) Automatically create 4LB virtual machines, corresponding to the real IPs: Rip1 and Rip2

[0050] b) Allocate exclusive floating IP: Vip1.

[0051] 2. Create 7LB instance 7lb1:

[0052] a) The service IP address needs to be in the same subnet as the 4lb IP address to facilitate DR mode forwarding;

[0053] b) Supports the following options: exclusive VIP (existing logic), or sharing VIP with a 4SLB instance. Here, we choose to share VIP with 4lb1.

[0054] c) Automatically create primary and backup 7lb virtual machines, corresponding to real IPs: Rip3 and Rip4;

[0055] d) After obtaining the floating IP of 4lb1, set the loopback IP to Vip1 on the two slb virtual machines;

[0056] 3. The control layer associates 4lb1 and 7lb1 for port management and allocation;

[0057] 4. Then create the 7LB listener 7lb-l1;

[0058] a) When setting the port, it is necessary to do association conflict detection with 4lb1;

[0059] b) There is no need to send keepalived configuration files and services;

[0060] c) Send the listener configuration file of 7lb-l1 normally;

[0061] d) It is also necessary to send the corresponding Layer 4 listener configuration of 7lb1-l1 on 4lb1 (DR mode; scheduling algorithm: WRR, hash value; no Lip required; health check: TCP_CHECK);

[0062] 5. In addition, 4lb1 can also create other four-layer listeners normally, such as Figure 2 Forward to RSa or RSb; however, 7lb1 can only be used in cascade with 4Slb1 and cannot provide high availability services independently of 4slb.

[0063] Reference Figure 2 , the service access four-layer LB request response process is described as follows:

[0064] 1. The client requests 20.20.20.20:53 through the public network, and obtains the private network floating IP 192.168.8.2:53 after NAT;

[0065] 2. 4lb1 forwards the packet to RSb through FNAT mode (modifies the source IP and source port and saves the session), and puts the real source IP into the protocol optional field (TOA / UOA);

[0066] 3. RSb obtains the source IP address and responds;

[0067] 4. After receiving the response, 4lb1 changes the destination IP and destination port to the client's and forwards it to the client.

[0068] Reference Figure 2 The request response process of business access to the four-layer LB and seven-layer LB cascade is described as follows:

[0069] 1. The client requests https: / / 20.20.20.20:443 through the public network, and obtains the private network floating IP after NAT, that is, accesses https: / / 192.168.8.2:443;

[0070] 2. 4lb1 forwards to 7lb1 in DR mode (only modify the destination mac);

[0071] 3. After receiving the request, 7lb1 directly obtains the source IP, and forwards it to RS3 in FNAT mode (modifies the source IP, source port and saves the session) according to the scheduling algorithm set by 7lb, and puts the real source IP into the HTTP protocol field;

[0072] 4. RS3 obtains the source IP address from the HTTP protocol header field and responds;

[0073] 5. After receiving the response, 7lb1 changes the destination IP and destination port to the client's and forwards it to the client.

[0074] It should be noted that the above describes some embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the above embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0075] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, an embodiment of the present application further provides a system implemented based on a method of load balancing and sharing floating IP resources.

[0076] like Figure 3 As shown, the system implemented by the method of sharing floating IP resources based on load balancing includes:

[0077] The cluster building module 11 is configured to build a cloud native load balancing cluster and configure a floating virtual IP and a virtual port for the cluster, wherein the cluster is composed of multiple LB servers;

[0078] The data request module 12 is configured to introduce the traffic of the client requesting the virtual IP to the currently active load balancing node in the load balancing cluster through the network device;

[0079] The cascade module 13 is configured to cascade the seven-layer load balancing cluster as a backend server with the four-layer load balancing cluster, and the four-layer load balancing cluster performs traffic parsing according to the port five-tuple information, and performs five-tuple hash scheduling of the four-layer load balancing cluster so that the same five-tuple request is always routed to the same seven-layer load balancing instance;

[0080] The request processing module 14 is configured as a seven-layer load balancing cluster to distribute requests to the backend business server according to its internal scheduling algorithm. After the backend business server processes the request, it returns the response data to the client through the seven-layer load balancing cluster and the four-layer load balancing cluster.

[0081] For the convenience of description, the above system is described by dividing the functions into various modules. Of course, when implementing the embodiments of the present application, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0082] The system of the above embodiment is used to implement the corresponding method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0083] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, an embodiment of the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the method described in any of the above embodiments is implemented.

[0084] Figure 4 A more specific schematic diagram of the hardware structure of an electronic device provided in this embodiment is shown, and the device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are connected to each other through the bus 1050 in the device.

[0085] The processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0086] The memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 may store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 1020 and are called and executed by the processor 1010.

[0087] The input / output interface 1030 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

[0088] The communication interface 1040 is used to connect a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).

[0089] The bus 1050 includes a path that transmits information between the various components of the device (eg, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).

[0090] It should be noted that, although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040 and the bus 1050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.

[0091] The electronic device of the above embodiment is used to implement the corresponding method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be described in detail here.

[0092] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments, the present application also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the method described in any of the above embodiments.

[0093] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

[0094] The computer instructions stored in the storage medium of the above embodiments are used to enable the computer to execute the method described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0095] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present application (including the claims) is limited to these examples. In line with the concept of the present application, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present application as described above, which are not provided in detail for the sake of simplicity.

[0096] In addition, to simplify the description and discussion, and in order not to make the embodiments of the present application difficult to understand, the known power supply / ground connection with the integrated circuit (IC) chip and other components may or may not be shown in the provided drawings. In addition, the device can be shown in the form of a block diagram to avoid making the embodiments of the present application difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform to be implemented in the embodiments of the present application (that is, these details should be fully within the scope of understanding of those skilled in the art). In the case of elaborating specific details (e.g., circuits) to describe exemplary embodiments of the present application, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details or when these specific details are changed. Therefore, these descriptions should be considered to be illustrative rather than restrictive.

[0097] Although the present application has been described in conjunction with specific embodiments of the present application, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.

[0098] The embodiments of the present application are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application should be included in the scope of protection of the present application.

Claims

1. A method for sharing floating IP resources based on load balancing, characterized in that: include: Build a cloud-native load balancing cluster and configure a floating virtual IP and a virtual port for the cluster, wherein the cluster consists of multiple LB servers; The client's request virtual IP traffic is introduced to the currently active load balancing node in the load balancing cluster through the network device; The seven-layer load balancing cluster is used as a backend server and cascaded with the four-layer load balancing cluster. The four-layer load balancing cluster performs traffic analysis based on the port five-tuple information and performs five-tuple hash scheduling of the four-layer load balancing cluster so that the same five-tuple request is always routed to the same seven-layer load balancing instance. The seven-layer load balancing cluster distributes the request to the backend business server according to its internal scheduling algorithm. After the backend business server processes the request, it returns the response data to the client through the seven-layer load balancing cluster and the four-layer load balancing cluster.

2. The method according to claim 1, characterized in that The method of introducing the traffic of the client requesting the virtual IP to the currently active load balancing node in the load balancing cluster through the network device includes: Services are provided externally through floating virtual IP and virtual port. The traffic of client requesting virtual IP is directed by network equipment to the server carrying floating virtual IP in the load balancing cluster. The server is dispatched to healthy business servers according to the scheduling algorithm, and then returns to the client after receiving the response.

3. The method according to claim 1, characterized in that: The hash value of the five-tuple is calculated by a hash algorithm to obtain a fixed scheduling result, and the request is allocated to a specific seven-layer load balancing instance according to the scheduling result.

4. The method according to claim 1, characterized in that: The four-layer load balancing cluster passes the original IP address of the client to the seven-layer load balancing cluster. In response to the seven-layer load balancing cluster forwarding the request to the backend business server, the real source IP address of the client is passed to the backend business server by adding an HTTP header field.

5. The method according to claim 1, characterized in that Also includes: Dynamically allocate port resources through automated tools, monitor port usage in real time, and dynamically adjust port allocation based on traffic load and business needs.

6. The method according to claim 1, characterized in that Also includes: Regularly perform health checks on the load balancing cluster nodes and backend business servers to detect whether they are in an available state.

7. The method according to claim 6, characterized in that: Health checks are performed through a combination of active detection and passive monitoring.

8. A system implemented based on a method for sharing floating IP resources with load balancing, characterized in that: include: A cluster building module is configured to build a cloud native load balancing cluster and configure a floating virtual IP and a virtual port for the cluster, wherein the cluster is composed of multiple LB servers; The data request module is configured to introduce the traffic of the client requesting the virtual IP to the currently active load balancing node in the load balancing cluster through the network device; The cascade module is configured to cascade the seven-layer load balancing cluster as a backend server with the four-layer load balancing cluster. The four-layer load balancing cluster performs traffic parsing according to the port five-tuple information, and performs five-tuple hash scheduling of the four-layer load balancing cluster so that the same five-tuple request is always routed to the same seven-layer load balancing instance. The request processing module is configured as a seven-layer load balancing cluster to distribute requests to the backend business server according to its internal scheduling algorithm. After the backend business server processes the request, it returns the response data to the client through the seven-layer load balancing cluster and the four-layer load balancing cluster.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 1 to 7 is implemented.

10. A non-transitory computer-readable storage medium, characterized in that: in, The non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to cause a computer to execute the method according to any one of claims 1 to 7.

Images