CN114020417A - Virtual load balancing system and working method thereof - Google Patents

Virtual load balancing system and working method thereof Download PDF

Info

Publication number
CN114020417A
CN114020417A CN202111363414.7A CN202111363414A CN114020417A CN 114020417 A CN114020417 A CN 114020417A CN 202111363414 A CN202111363414 A CN 202111363414A CN 114020417 A CN114020417 A CN 114020417A
Authority
CN
China
Prior art keywords
virtual
request
data packet
virtual machine
network card
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202111363414.7A
Other languages
Chinese (zh)
Inventor
石磊
张辉
马亮
姜健
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shandong Trusted Cloud Information Technology Research Institute
Shandong Qianyun Qichuang Information Technology Co ltd
Original Assignee
Shandong Trusted Cloud Information Technology Research Institute
Shandong Qianyun Qichuang Information Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shandong Trusted Cloud Information Technology Research Institute, Shandong Qianyun Qichuang Information Technology Co ltd filed Critical Shandong Trusted Cloud Information Technology Research Institute
Priority to CN202111363414.7A priority Critical patent/CN114020417A/en
Publication of CN114020417A publication Critical patent/CN114020417A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/50Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/505Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the load
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/50Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061Partitioning or combining of resources
    • G06F9/5077Logical partitioning of resources; Management or configuration of virtualized resources
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/4557Distribution of virtual machine instances; Migration and load balancing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45583Memory management, e.g. access or allocation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45595Network integration; Enabling network access in virtual machine instances
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00Indexing scheme relating to G06F9/00
    • G06F2209/50Indexing scheme relating to G06F9/50
    • G06F2209/5021Priority

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The virtual load balancing system runs in a host machine, and comprises a load balancer virtual network card, a virtual load balancer and a plurality of virtual machines running on the host machine, wherein the virtual load balancer comprises a request module and a response module; the request module is used for acquiring an external service request based on the load balancer virtual network card and delivering a request data packet to a request queue; the virtual machine is used for applying for acquiring a request data packet from the request queue by using a virtual network card of the virtual machine, generating a response data packet after being processed by service application in the virtual machine, and delivering the response data packet to the response queue through the virtual network card of the virtual machine; and the response module is used for taking out a response data packet from the response queue and returning the response data packet to the client sending the service request through the virtual network card of the load balancer.

Description

Virtual load balancing system and working method thereof
Technical Field
The disclosure belongs to the technical field of cloud computing, and particularly relates to a virtual load balancing system and a working method thereof.
Background
The statements in this section merely provide background information related to the present disclosure and may not necessarily constitute prior art.
In a cloud computing/virtualization scenario, a situation that a virtual machine cluster is used for processing services is very common, and load balancing is a key link. Load balancing solves two problems: firstly, the virtual machines which are currently active are automatically identified, and only service requests are distributed to the virtual machines; and secondly, in the active virtual machines, the current load is light or the processing capacity is strong.
The inventor finds that the existing load balancing method mainly comprises the following steps:
(1) and distributing the traffic load to each virtual machine by using a hardware load balancer. All virtual machines are regarded as physical machines, and the traditional scheme is directly adopted; however, using a traditional hardware form of load balancer in a virtualized environment has two problems: firstly, the cost of purchasing hardware is high; secondly, the difference between the traditional environment and the virtualization environment cannot be considered, and the working efficiency is not high.
(2) The virtual load balancer is implemented at the software level, but the push mode is mainly adopted at present. That is, the load balancer needs to actively poll and detect the active virtual machines and select the one with a lighter load as a target, and then forward the service data to the target virtual machine in a push manner. However, in the current various virtual load balancer implementations, it is necessary to detect whether all the virtual machines are working normally online, and further, it is necessary to detect their respective load conditions, and then the target forwarding service data can be selected. According to this technique, the load balancer is heavy in workload and complicated to implement. In addition, the load balancer must know exactly the number of virtual machines and the IP of each virtual machine to support polling detection, which causes great inconvenience to the dynamic scaling of the virtual machine cluster.
Disclosure of Invention
In order to solve the above problems, the present disclosure provides a virtual load balancing system and a working method thereof, which can implement load balancing of network requests for any number of virtual machines in the same host.
According to a first aspect of the embodiments of the present disclosure, a virtual load balancing system is provided, which runs in a host, and the system includes a load balancer virtual network card, a virtual load balancer, and a plurality of virtual machines running on the host, wherein the virtual load balancer includes a request module and a response module;
the request module is used for acquiring an external service request based on the load balancer virtual network card and delivering a request data packet to a request queue;
the virtual machine is used for applying for acquiring a request data packet from the request queue by using a virtual network card of the virtual machine, generating a response data packet after being processed by service application in the virtual machine, and delivering the response data packet to the response queue through the virtual network card of the virtual machine;
and the response module is used for taking out a response data packet from the response queue and returning the response data packet to the client sending the service request through the virtual network card of the load balancer.
Further, the load balancer virtual network card is a TAP device bridged on a host machine physical network card.
Further, the specific steps of the virtual network cards of the virtual machines acquiring the request data packets from the request queue are as follows: when the request queue is empty, all the virtual machines enter a waiting state; when the request queue is not empty, allocating request data packets in sequence according to the application time of the virtual machine;
or, when the request queue is not empty, selecting the virtual machine to distribute the request data packet in a random mode;
or when the request queue is not empty, distributing the request data packets according to the priority order of the virtual machines, and selecting the virtual machines at the same priority in a random mode.
Further, the virtual machine applying for obtaining the request data packet from the request queue has the following constraints:
(1) only the virtual machine in the running state participates in acquiring the request data packet;
(2) based on the processing capacity and the running state of the virtual machines, priority control is carried out when different virtual machines apply for acquiring the request data packet, and the acquisition request data packet is preceded by the higher priority.
Further, the priority control specifically includes: the priority of the virtual machine in the idle state is higher than that of the virtual machine in the busy state, and the priority of the virtual machine with strong processing capability is higher than that of the virtual machine with weak processing capability.
According to a second aspect of the embodiments of the present disclosure, there is provided a working method of a virtual load balancing system, including:
the client sends out a service request data packet by taking the IP of the virtual network card of the load balancer as a target IP;
the virtual load balancer delivers the request data packet to the request queue;
the virtual machine in the host machine acquires the request data packet based on the priority strategy, performs service processing by using service application in the virtual machine, and the virtual network card delivers a response data packet obtained by the service processing to a response queue;
and the virtual load balancer returns the response data packet to the client of the service request.
Compared with the prior art, the beneficial effect of this disclosure is:
(1) the scheme of the disclosure provides a virtual load balancing system, which provides a network request load balancing service for multiple virtual machines on the same host machine by introducing a virtual load balancer.
(2) Compared with the existing software load balancer implementation, the scheme disclosed by the invention does not need the load balancer to inquire the running state and the load condition of each virtual machine, and the implementation difficulty is relatively low.
(3) Compared with the existing software load balancer implementation, the method does not need the load balancer to know the number of the virtual machine clusters and the IP of each virtual machine, thereby being beneficial to the dynamic expansion and contraction of the virtual machine clusters.
Advantages of additional aspects of the disclosure will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the disclosure.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure, illustrate embodiments of the disclosure and together with the description serve to explain the disclosure and are not to limit the disclosure.
Fig. 1 is a schematic structural diagram of a virtual load balancing system according to a first embodiment of the present disclosure;
fig. 2 is a flowchart illustrating processing a request by a virtual load balancer according to a second embodiment of the disclosure;
fig. 3 is a flowchart of processing a request and returning a response by virtual load balancing according to a second embodiment of the present disclosure;
fig. 4 is a flowchart of a virtual load balancing processing response according to the second embodiment of the present disclosure.
Detailed Description
The present disclosure is further described with reference to the following drawings and examples.
It should be noted that the following detailed description is exemplary and is intended to provide further explanation of the disclosure. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
It is noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments according to the present disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, and it should be understood that when the terms "comprises" and/or "comprising" are used in this specification, they specify the presence of stated features, steps, operations, devices, components, and/or combinations thereof, unless the context clearly indicates otherwise.
The embodiments and features of the embodiments in the present disclosure may be combined with each other without conflict.
Interpretation of professional terms:
the TAP device is a link layer virtual network device, which is equivalent to an ethernet device, and can transmit and receive a second layer data packet, such as an ethernet data frame. The most common use of TAP is as a network card for virtual machines, since it is more similar to a common physical network card and is often used as a virtual network card for common machines.
The first embodiment is as follows:
the present embodiment aims to provide a virtual load balancing system.
A virtual load balancing system runs in a host machine and comprises a load balancer virtual network card, a virtual load balancer and a plurality of virtual machines running on the host machine, wherein the virtual load balancer comprises a request module and a response module;
the request module is used for acquiring an external service request based on the load balancer virtual network card and delivering a request data packet to a request queue;
the virtual machine is used for applying for acquiring a request data packet from the request queue by using a virtual network card of the virtual machine, generating a response data packet after being processed by service application in the virtual machine, and delivering the response data packet to the response queue through the virtual network card of the virtual machine;
and the response module is used for taking out a response data packet from the response queue and returning the response data packet to the client sending the service request through the virtual network card of the load balancer.
Further, the load balancer virtual network card is a TAP device bridged on a host machine physical network card.
Furthermore, each virtual machine running in the host machine has an independent virtual network card.
Further, the specific steps of the virtual network cards of the virtual machines acquiring the request data packets from the request queue are as follows: when the request queue is empty, all the virtual machines enter a waiting state; when the request queue is not empty, allocating request data packets in sequence according to the application time of the virtual machine;
or, when the request queue is not empty, selecting the virtual machine to distribute the request data packet in a random mode;
or when the request queue is not empty, distributing the request data packets according to the priority order of the virtual machines, and selecting the virtual machines at the same priority in a random mode.
Further, the virtual machine applying for obtaining the request data packet from the request queue has the following constraints:
(1) only the virtual machine in the running state participates in acquiring the request data packet;
(2) based on the processing capacity and the running state of the virtual machines, priority control is carried out when different virtual machines apply for acquiring the request data packet, and the acquisition request data packet is preceded by the higher priority.
Further, the priority control specifically includes: the priority of the virtual machine in the idle state is higher than that of the virtual machine in the busy state, and the priority of the virtual machine with strong processing capability is higher than that of the virtual machine with weak processing capability.
Further, the processing capability is embodied in the amount of the memory and the CPU core allocated by the virtual machine.
Specifically, for ease of understanding, the embodiments of the present disclosure are described in detail below with reference to the accompanying drawings:
as shown in fig. 1, the present disclosure provides a virtual load balancing system, which includes a load balancer virtual network card, a virtual load balancer, and a plurality of virtual machines running on a host, wherein:
and bridging a TAP device on a physical network card of the host machine to serve as a virtual network card of a load balancer, and setting an I P address as a I P address of the load balancing external service.
The virtual load balancer is a process running on a host machine, and comprises two working threads, a request thread and a response thread, and the request thread and the response thread correspond to the request module and the response module.
Simultaneously, be provided with two queues on the host computer, wherein: the request queue stores service request data packets from clients, and the response queue stores response data packets which are processed by the virtual machine and then fed back.
Further, the whole system process consists of three asynchronous concurrently running parts:
(1) process for load balancer delivery request
The virtual load balancer's request thread waits on the TAP device for a service request from the outside and then posts a request packet into the request queue.
(2) Process for virtual machine to respond to request and return reply
Each virtual machine is provided with a virtual network card, and the virtual network card takes out the request data packet from the request queue and transfers the request data packet into the virtual machine through the drive of the virtual network card. And after the service application processes the request, response data is generated and then is transmitted to the virtual network card through the virtual network card drive, and finally the response data is delivered to a response queue by the virtual network card.
(3) Process for load balancer to return response
And the response thread of the virtual load balancer takes out the response data packet from the response queue and then returns the response data packet to the client sending the service request through the network.
Further, at the virtual machine end, a plurality of virtual machines are usually operated, and the specific steps of the virtual network cards of the virtual machines acquiring the request data packets from the request queue are as follows:
the specific steps of the virtual network cards of the virtual machines acquiring the request data packets from the request queue are as follows: when the request queue is empty, all the virtual machines enter a waiting state; when the request queue is not empty, allocating request data packets in sequence according to the application time of the virtual machine;
or, when the request queue is not empty, selecting the virtual machine to distribute the request data packet in a random mode;
or when the request queue is not empty, distributing the request data packets according to the priority order of the virtual machines, and selecting the virtual machines at the same priority in a random mode.
Further, according to the above principle, the virtual machine that applies for obtaining the request packet from the request queue has the following constraints:
(1) only the virtual machine in the running state participates in acquiring the request data packet;
(2) based on the processing capacity and the running state of the virtual machines, priority control is carried out when different virtual machines apply for acquiring the request data packet, and the acquisition request data packet is preceded by the higher priority.
In conclusion, the virtual machines can automatically coordinate to achieve the effect of load balancing, and the load balancer only needs to transmit and receive data facing to the queue, and does not need to detect the running state and the load condition of each virtual machine.
Example two:
the embodiment aims to provide a working method of a virtual load balancing system.
A working method of a virtual load balancing system comprises the following steps:
the client sends out a service request data packet by taking the IP of the virtual network card of the load balancer as a target IP;
the virtual load balancer delivers the request data packet to the request queue;
the virtual machine in the host machine acquires the request data packet based on the priority strategy, performs service processing by using service application in the virtual machine, and the virtual network card delivers a response data packet obtained by the service processing to a response queue;
and the virtual load balancer returns the response data packet to the client of the service request.
Further, the priority policy specifically includes: the priority of the virtual machine in the idle state is higher than that of the virtual machine in the busy state, the priority of the virtual machine with strong processing capability is higher than that of the virtual machine with weak processing capability, and the acquisition request data packet with high priority is prior to the acquisition request data packet with low priority.
Furthermore, each virtual machine running in the host machine has an independent virtual network card.
Specifically, for ease of understanding, the embodiments of the present disclosure are described in detail below with reference to the accompanying drawings:
as shown in fig. 1 to fig. 3, the working method of the virtual load balancing system according to the present disclosure includes four aspects, namely a preparation process, a request process, a processing process, and a response process, and the following four aspects are respectively explained:
the preparation process comprises the following steps: a TAP device is created that is connected to the host physical network card in a bridge fashion. And configuring the IP of the TAP equipment, wherein the IP of the TAP equipment is the IP address of the external service of the load balancer.
1. Load balancer processing request flow (as shown in FIG. 2)
1.1 the client sends out service request data packet with load balanced external IP (i.e. TAP equipment IP) as target IP.
1.2 service request data packet reaches TAP equipment through host machine network card (bridge mode).
1.3 the load balancer fetches a request packet from the TAP device.
1.4 the load balancer posts request packets into the request queue.
2. Virtual machine processing request and return response flow (as shown in FIG. 3)
2.1 the virtual network card competes on the request queue to obtain the requested data packet. If success, 2.2 is entered, otherwise, the competition for the next one is continued.
2.2 the virtual network card informs the virtual network card driver. The virtual driver stores the request data packet into a network data buffer area managed by an internal operating system of the virtual machine; meanwhile, the source IP of the request data packet is kept unchanged, and the target IP is changed into the IP of the virtual network card.
And 2.3, the virtual network card driver informs the service application through a Socket interface. And after being awakened, the service application reads a request from a system network data buffer area through a Socket interface and then performs service processing.
And 2.4, the service application transmits the response data packet to the virtual network card driver for processing through the Socket interface after processing the request.
And 2.5, the virtual network card driver submits the response data packet to the virtual network card.
2.6 the virtual network card delivers the response data packet to the response queue.
3. Load balancer processing response flow (as shown in FIG. 4)
3.1 the load balancer waits in the acknowledgement queue. And taking out a response data packet when the queue is not empty.
3.2 the load balancer changes the source IP of the reply packet to its own IP (i.e., the IP of the external service for load balancing), and then sends the reply through the TAP device.
3.3 the reply packet is sent to the external network via the host network card (bridge mode).
3.4 the reply packet is eventually returned to the service requesting client.
The virtual load balancing system and the working method thereof provided by the embodiment can be realized, and have wide application prospects.
The above description is only a preferred embodiment of the present disclosure and is not intended to limit the present disclosure, and various modifications and changes may be made to the present disclosure by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present disclosure should be included in the protection scope of the present disclosure.

Claims (10)

1. A virtual load balancing system runs in a host machine and is characterized by comprising a load balancer virtual network card, a virtual load balancer and a plurality of virtual machines running on the host machine, wherein the virtual load balancer comprises a request module and a response module;
the request module is used for acquiring an external service request based on the load balancer virtual network card and delivering a request data packet to a request queue;
the virtual machine is used for applying for acquiring a request data packet from the request queue by using a virtual network card of the virtual machine, generating a response data packet after being processed by service application in the virtual machine, and delivering the response data packet to the response queue through the virtual network card of the virtual machine;
and the response module is used for taking out a response data packet from the response queue and returning the response data packet to the client sending the service request through the virtual network card of the load balancer.
2. The virtual load balancing system of claim 1, wherein the load balancer virtual network card is a TAP device that bridges over a host physical network card.
3. The virtual load balancing system of claim 1, wherein each virtual machine running in the host machine has an independent virtual network card.
4. The virtual load balancing system according to claim 1, wherein the specific steps of the virtual network cards of the virtual machines acquiring the request data packets from the request queue are as follows: when the request queue is empty, all the virtual machines enter a waiting state; when the request queue is not empty, allocating request data packets in sequence according to the application time of the virtual machine;
or, when the request queue is not empty, selecting the virtual machine to distribute the request data packet in a random mode;
or when the request queue is not empty, distributing the request data packets according to the priority order of the virtual machines, and selecting the virtual machines at the same priority in a random mode.
5. The virtual load balancing system of claim 1, wherein the virtual machines requesting for the requested packet from the request queue have the following constraints:
(1) only the virtual machine in the running state participates in acquiring the request data packet;
(2) based on the processing capacity and the running state of the virtual machines, priority control is carried out when different virtual machines apply for acquiring the request data packet, and the acquisition request data packet is preceded by the higher priority.
6. The virtual load balancing system according to claim 5, wherein the priority control specifically comprises: the priority of the virtual machine in the idle state is higher than that of the virtual machine in the busy state, and the priority of the virtual machine with strong processing capability is higher than that of the virtual machine with weak processing capability.
7. The virtual load balancing system of claim 6, wherein the processing power is embodied in the amount of memory and CPU cores allocated by the virtual machine.
8. A working method of a virtual load balancing system is characterized by comprising the following steps:
the client sends out a service request data packet by taking the IP of the virtual network card of the load balancer as a target IP;
the virtual load balancer delivers the request data packet to the request queue;
the virtual machine in the host machine acquires the request data packet based on the priority strategy, performs service processing by using service application in the virtual machine, and the virtual network card delivers a response data packet obtained by the service processing to a response queue;
and the virtual load balancer returns the response data packet to the client of the service request.
9. The operating method of a virtual load balancing system according to claim 8, wherein the priority policy specifically includes: the priority of the virtual machine in the idle state is higher than that of the virtual machine in the busy state, the priority of the virtual machine with strong processing capability is higher than that of the virtual machine with weak processing capability, and the acquisition request data packet with high priority is prior to the acquisition request data packet with low priority.
10. The method of claim 8, wherein each virtual machine running on the host has an independent virtual network card.
CN202111363414.7A 2021-11-17 2021-11-17 Virtual load balancing system and working method thereof Pending CN114020417A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111363414.7A CN114020417A (en) 2021-11-17 2021-11-17 Virtual load balancing system and working method thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111363414.7A CN114020417A (en) 2021-11-17 2021-11-17 Virtual load balancing system and working method thereof

Publications (1)

Publication Number Publication Date
CN114020417A true CN114020417A (en) 2022-02-08

Family

ID=80064757

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111363414.7A Pending CN114020417A (en) 2021-11-17 2021-11-17 Virtual load balancing system and working method thereof

Country Status (1)

Country Link
CN (1) CN114020417A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024067525A1 (en) * 2022-09-27 2024-04-04 杭州阿里云飞天信息技术有限公司 Load balancing method, server, data center network system and electronic device

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024067525A1 (en) * 2022-09-27 2024-04-04 杭州阿里云飞天信息技术有限公司 Load balancing method, server, data center network system and electronic device

Similar Documents

Publication Publication Date Title
US10171567B2 (en) Load balancing computer device, system, and method
US10698717B2 (en) Accelerator virtualization method and apparatus, and centralized resource manager
US5991797A (en) Method for directing I/O transactions between an I/O device and a memory
US7840683B2 (en) Systems and methods of migrating sessions between computer systems
EP0362107B1 (en) Method to manage concurrent execution of a distributed application program by a host computer and a large plurality of intelligent work stations on an SNA network
WO2018035856A1 (en) Method, device and system for implementing hardware acceleration processing
EP2321937B1 (en) Load balancing for services
US9990306B2 (en) Inter-manycore communications method and system
US20020199000A1 (en) Method and system for managing parallel data transfer through multiple sockets to provide scalability to a computer network
EP1748598B1 (en) System, method and server for ensuring a device uses the correct instance of a network service
WO2021120633A1 (en) Load balancing method and related device
CN108293041A (en) A kind of distribution method of resource, device and system
JP2000029856A (en) Task allocating method, data processing system, client data processing node, and machine readable storage medium
US8849905B2 (en) Centralized computing
CN111787079B (en) Communication method, device, server, system and medium based on communication group
CN111404931B (en) Remote data transmission method based on persistent memory
CN110830574B (en) Method for realizing intranet load balance based on docker container
CN111970362A (en) Vehicle networking gateway clustering method and system based on LVS
CN114020417A (en) Virtual load balancing system and working method thereof
WO2014101502A1 (en) Memory access processing method based on memory chip interconnection, memory chip, and system
JP2003016031A (en) Control system for priority connection for client/server system
KR102119456B1 (en) Distributed Broker Coordinator System and Method in a Distributed Cloud Environment
US20230205418A1 (en) Data processing system and operating method thereof
CN106790632B (en) Streaming data concurrent transmission method and device
CN115766729A (en) Data processing method for four-layer load balancing and related device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination