CN112118291B - Load balancing system and method for service flow - Google Patents
Load balancing system and method for service flow Download PDFInfo
- Publication number
- CN112118291B CN112118291B CN202010813794.9A CN202010813794A CN112118291B CN 112118291 B CN112118291 B CN 112118291B CN 202010813794 A CN202010813794 A CN 202010813794A CN 112118291 B CN112118291 B CN 112118291B
- Authority
- CN
- China
- Prior art keywords
- application program
- service
- program node
- service type
- node information
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1012—Server selection for load balancing based on compliance of requirements or conditions with available server resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a load balancing system and method for service traffic, wherein an application program in an entity server is registered in a corresponding zookeeper cluster to generate an application program node registry, and the application program node registry comprises application program node information and a service type corresponding to the application program node information. After a data input port of a load scheduler receives service traffic, the load scheduler searches target application program node information capable of providing the service type required by the service traffic in an application program node registry of the zookeeper cluster according to the service type required by the service traffic. And the main bottom layer scheduling software LVS and keepalived of the load scheduler distributes the service flow to the application program corresponding to the target application program node information in the entity server. And processing of various service flows is realized. The expansion of the service types can be realized by installing the application program on the server, and the processing capacity of the service flow is improved.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a system and a method for load balancing of service traffic.
Background
Load Balance (Load Balance) is to share a plurality of operation units to execute, such as a Web server, an FTP server, an enterprise key application server, and other key task servers, so as to collectively complete work tasks.
The server using hardware realizes foreground and background service flow load balancing, and the adoption of hardware load balancing not only needs maintenance personnel to carry out manual configuration, increases the workload and the error rate of maintenance, but also can process the type of service flow, and is difficult to linearly expand.
Disclosure of Invention
In view of this, embodiments of the present invention provide a system and a method for load balancing of service traffic, so as to solve technical defects in the prior art.
The embodiment of the invention discloses a load balancing system and a method of service flow, which comprises the following steps:
the system comprises an entity server, a service type server and a service flow server, wherein the entity server is provided with a plurality of application programs, and each application program can process the service flow corresponding to one service type;
the zookeeper cluster can receive application program node registration information sent by the entity server, the application program is registered in the corresponding zookeeper cluster to generate an application program node registry, and the application program node registry comprises application program node information and a service type corresponding to the application program node information;
the load scheduler is provided with a data input port and a data output port, the data input port of the load scheduler can receive service flow, the data output port of the load scheduler is connected with the entity server, and the load scheduler deploys an agent, main bottom layer scheduling software LVS and a keepalive;
according to the service type required by the service flow received by the data input port of the load scheduler, searching target application program node information capable of providing the service type required by the service flow in an application program node registry of the zookeeper cluster;
and according to the target application program node information searched in the zookeeper cluster, the main bottom layer scheduling software LVS and the keepalive of the load scheduler distribute the service flow to the application program corresponding to the target application program node information in the entity server.
The embodiment of the invention also discloses a load balancing method of service flow, which comprises the following steps:
configuring an entity server, wherein the entity server is provided with a plurality of application programs, and each application program can process service flow corresponding to one service type;
configuring a zookeeper cluster, wherein the zookeeper cluster can receive application program node registration information sent by the entity server, the application program is registered in the corresponding zookeeper cluster to generate an application program node registry, and the application program node registry comprises application program node information and a service type corresponding to the application program node information;
configuring a load scheduler, wherein the load scheduler is provided with a data input port and a data output port, the data input port of the load scheduler can receive service flow, the data output port of the load scheduler is connected with an entity server, and the load scheduler deploys an agent, main bottom layer scheduling software LVS and a keepalive;
searching target application program node information capable of providing the service type required by the service flow in an application program node registry of the zookeeper cluster according to the service type required by the service flow received by a data input port of the load scheduler;
and according to the target application program node information searched in the zookeeper cluster, the main bottom layer scheduling software LVS and the keepalive of the load scheduler distribute the service flow to the application program corresponding to the target application program node information in the entity server.
The invention provides a load balancing system and method for service traffic, which are characterized in that an application program in an entity server is registered in a corresponding zookeeper cluster to generate an application program node registry, and the application program node registry comprises application program node information and a service type corresponding to the application program node information.
Then, after a data input port of the load scheduler receives a service flow, the load scheduler searches for target application program node information capable of providing the service type required by the service flow in an application program node registry of the zookeeper cluster according to the service type required by the service flow. And finally, distributing the service flow to an application program corresponding to the target application program node information in the entity server by using main bottom layer scheduling software LVS and keepalive of the load scheduler.
And according to the service type required by the service flow, installing an application program capable of processing the service flow corresponding to the required service type on the entity server, and realizing the processing of various service flows. The expansion of the service types can be realized by installing the application program on the server, and the processing capacity of the service flow is improved.
Drawings
Fig. 1 is a schematic structural diagram of a load balancing system for traffic according to an embodiment of the present invention.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. This invention may be embodied in many different forms than those herein set forth and should be readily appreciated by those skilled in the art without departing from the spirit and scope of the invention as defined by the appended claims.
The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present specification refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It will be understood that, although the terms first, second, etc. may be used herein in one or more embodiments to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first can also be referred to as a second and, similarly, a second can also be referred to as a first without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at" \8230; "or" when 8230; \8230; "or" in response to a determination ", depending on the context.
In the present invention, a load balancing system for traffic is provided, which is described in detail in the following embodiments one by one.
Fig. 1 is a schematic structural diagram illustrating a load balancing system for traffic according to an embodiment of the present invention, including:
and the entity server 10 is provided with a plurality of application programs, and each application program can process the service flow corresponding to one service type.
The application program is installed as app in the entity server 10 1 、app 2 And app n E.g. apps 1 The type of service that can be handled is package flow query, app 2 The type of service that can be handled is package handling.
Different service flows need to be processed by corresponding application programs, for example, if the service type corresponding to the service flow is package flow query, the service flow is query request data, and then the package flow is needed to query corresponding application program apps 1 To handle traffic flow.
The zookeeper cluster 20 can receive application program node registration information sent by the entity server 10, the application program is registered in the corresponding zookeeper cluster 20 to generate an application program node registry, and the application program node registry comprises the application program node information and a service type corresponding to the application program node information;
the ZooKeeper cluster 20 is an open source distributed application coordination service.
Installing an application app in the entity server 10 1 、app 2 And app n Then, the zookeeper cluster 20 can receive the application node registration information sent by the entity server 10, and the application program is registered in the corresponding zookeeper cluster 20 to generate an application node registry, so as to determine the app in the entity server 10 1 To app n The service type of the app belongs to when the entity server starts 1 To app n And registering the service types to form a tree-shaped service structure.
The characteristics of the tree data structure and the watchdog mechanism of the ZooKeeper cluster 20 are utilized, so that the following steps can realize the distribution of the service traffic by calling the application program node registry through the ZooKeeper cluster 20.
The application node information may include an application name, an application version, an application installation path, and an application installation time.
The system comprises a load scheduler 30, wherein the load scheduler 30 is provided with a data input port and a data output port, the data input port of the load scheduler can receive traffic flow, the data output port of the load scheduler 30 is connected with an entity server, and the load scheduler deploys an agent, main bottom layer scheduling software LVS and keepalived;
the load scheduler 30 is a process scheduler that can allocate the computing power of the CPU as needed. For example, the load scheduler 30 may be a Linux scheduler (BFS), a Linux scheduler is a kernel scheduler designed for a Linux desktop environment, and the load scheduler 30 may be of other types.
According to the service type required by the service traffic received by the data input port of the load scheduler 30, searching target application node information capable of providing the service type required by the service traffic in the application node registry of the zookeeper cluster 20.
For example, the service type required by the received service traffic is package traffic query, and target application node information capable of providing the service type required by the service traffic is searched in the application node registry of the zookeeper cluster 20 to be app 1 。
And according to the target application program node information searched in the zookeeper cluster, the main bottom layer scheduling software LVS and keepalive of the load scheduler distribute the service flow to the application program corresponding to the target application program node information in the entity server.
I.e. distributing the traffic to apps in entity servers 1 Through app 1 To handle traffic flow.
In the invention, an application program node registry is generated by registering an application program in an entity server 10 into the corresponding zookeeper cluster, wherein the application program node registry comprises application program node information and a service type corresponding to the application program node information.
Then, after the data input port of the load scheduler receives the service traffic, the load scheduler searches for target application program node information capable of providing the service type required by the service traffic in the application program node registry of the zookeeper cluster according to the service type required by the service traffic. And finally, distributing the service flow to an application program corresponding to the target application program node information in the entity server by using main bottom layer scheduling software LVS and keepalive of the load scheduler.
According to the service type required by the service flow, an application program capable of processing the service flow corresponding to the required service type is installed on the entity server 10, so that the processing of various service flows is realized.
In the actual service flow processing work, the service types required by the service flow are as many as twenty, the service types are gradually increased along with the expansion of the service, new application programs are correspondingly developed when the new service types are increased, the expansion of the service types can be realized by directly installing the new application programs on the server, the new application programs can process the service flow corresponding to the new service types, and the service flow processing capacity is improved.
The LVS is an abbreviation of Linux Virtual Server, and the main function of the LVS is to realize load balancing. Its availability = available time/(available time + failure recovery time), typically expressed in percentage; 99.9% means a failure time of less than 8 hours for one year; 99.99% indicates a failure time of less than 53 minutes for one year; 99.999% indicates a failure time of less than 5 minutes for one year.
keepalived is used to manage and monitor the status of each node in the LVS cluster.
And under the condition that the entity server installs a new application program or uninstalls the application program, the ZooKeeper cluster updates the application program node registry. And ensuring that the scheduler can reliably distribute the application program corresponding to the service flow.
The system for load balancing of the service traffic further comprises:
the management platform 40 acquires node information registered by an application program through a detection module of the zookeeper cluster;
the management platform 40 obtains the loadable service type through the node information registered by the application program, and automatically accesses the loadable service type and the unloaded service type according to the loadable service type. The management platform 40 realizes automatic online and offline of service types, and improves management efficiency.
In addition, the management platform 40 can manage keepalived through agent configuration. The management platform 40 is able to access information of the management platform configuration through the management platform database 50.
The load scheduler also deploys agent, alternate bottom layer scheduling software LVS and keepalived;
in order to prevent the situation that the workload of the main bottom layer scheduling software LVS and the keepalive is too large, which causes the traffic distribution jam and even the fault, the traffic is distributed in an auxiliary way through the standby bottom layer scheduling software LVS and the keepalive under the condition that the traffic distribution rate of the main bottom layer scheduling software LVS and the keepalive exceeds the processing threshold. The smooth distribution of the service flow to the application programs in the entity server is ensured, and the availability of the load scheduler is improved.
The invention also provides a load balancing method of the service flow, which comprises the following steps:
configuring an entity server, wherein the entity server is provided with a plurality of application programs, and each application program can process service flow corresponding to one service type;
configuring a zookeeper cluster, wherein the zookeeper cluster can receive application program node registration information sent by the entity server, the application program is registered in the corresponding zookeeper cluster to generate an application program node registry, and the application program node registry comprises application program node information and a service type corresponding to the application program node information;
configuring a load scheduler, wherein the load scheduler is provided with a data input port and a data output port, the data input port of the load scheduler can receive service flow, the data output port of the load scheduler is connected with an entity server, and the load scheduler deploys an agent, main bottom layer scheduling software LVS and a keepalive;
searching target application program node information capable of providing the service type required by the service flow in an application program node registry of the zookeeper cluster according to the service type required by the service flow received by a data input port of the load scheduler;
and according to the target application program node information searched in the zookeeper cluster, the main bottom layer scheduling software LVS and keepalive of the load scheduler distribute the service flow to the application program corresponding to the target application program node information in the entity server.
The method for balancing the load of the service traffic further comprises the following steps: configuring a management platform, wherein the management platform acquires node information registered by an application program through a detection module of the zookeeper cluster; the management platform acquires the loadable service type through the registered node information of the application program, and automatically loads the online loadable service type and the offline unloadable service type according to the loadable service type.
And under the condition that the entity server installs a new application program or uninstalls the application program, the ZooKeeper cluster updates the application program node registry.
The load scheduler also deploys agent, alternate bottom layer scheduling software LVS and keepalived; and under the condition that the service flow rate distributed by the main bottom layer scheduling software LVS and the keepalive exceeds a processing threshold, the service flow is distributed in an auxiliary manner through the standby bottom layer scheduling software LVS and the keepalive.
The method for load balancing of service traffic in this embodiment is consistent with the concept of the load balancing system of service traffic, and reference is made to the description of the load balancing system of service traffic, which is not described herein again.
It should be noted that, for the sake of simplicity, the above-mentioned method embodiments are described as a series of acts or combinations, but those skilled in the art should understand that the present invention is not limited by the described order of acts, as some steps may be performed in other orders or simultaneously according to the present invention. Further, those skilled in the art will appreciate that the embodiments described in this specification are presently considered to be preferred embodiments and that no single act or module is essential to the invention.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to the related descriptions of other embodiments.
The preferred embodiments of the invention disclosed above are intended to be illustrative only. Alternative embodiments are not exhaustive and do not limit the invention to the precise embodiments described. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the invention and the practical application, to thereby enable others skilled in the art to best utilize the invention. The invention is limited only by the claims and their full scope and equivalents.
Claims (4)
1. A system for load balancing traffic, comprising:
an entity server that installs a plurality of application apps 1 、app 2 And app n Each application program can process the service flow corresponding to one service type;
the zookeeper cluster can receive application program node registration information sent by the entity server, the application program is registered in the corresponding zookeeper cluster to generate an application program node registration table, the application program node registration table comprises application program node information and service types corresponding to the application program node information, and the application program node information comprises an application name, an application version, an application installation path and application installation time; determining apps in the entity server 1 To app n A service type to which the app belongs, the app being executed when the entity server is started 1 To app n Registering the service type to form a tree-shaped service structure;
the load scheduler is provided with a data input port and a data output port, the data input port of the load scheduler can receive service flow, the data output port of the load scheduler is connected with the entity server, and the load scheduler deploys an agent, main bottom layer scheduling software LVS and a keepalive;
according to the service type required by the service flow received by the data input port of the load scheduler, searching target application program node information capable of providing the service type required by the service flow in an application program node registry of the zookeeper cluster;
according to the target application program node information searched in the zookeeper cluster, the main bottom layer scheduling software LVS and keepalive of the load scheduler distribute the service flow to an application program corresponding to the target application program node information in an entity server;
the load scheduler also deploys an agent, a bottom layer preparation scheduling software LVS and a keepalived;
and under the condition that the service flow rate distributed by the main bottom layer scheduling software LVS and the keepalive exceeds a processing threshold, the service flow is distributed in an auxiliary manner through the standby bottom layer scheduling software LVS and the keepalive.
2. The system for load balancing of traffic according to claim 1, further comprising:
the management platform acquires node information registered by an application program through a detection module of the zookeeper cluster;
the management platform acquires the loadable service type through the registered node information of the application program, and automatically loads the online loadable service type and the offline unloadable service type according to the loadable service type.
3. The system for load balancing of traffic according to claim 2, wherein the z-ookeepers cluster updates the application node registry when the entity server installs a new application or uninstalls an application.
4. A method for load balancing of service traffic is characterized by comprising the following steps:
configuring an entity server, wherein the entity server is provided with a plurality of application programs, and each application program can process service flow corresponding to one service type;
configuring a zookeeper cluster, wherein the zookeeper cluster can receive application program node registration information sent by the entity server, the application program is registered in the corresponding zookeeper cluster to generate an application program node registry, and the application program node registry comprises application program node information and a service type corresponding to the application program node information;
configuring a load scheduler, wherein the load scheduler is provided with a data input port and a data output port, the data input port of the load scheduler can receive service flow, the data output port of the load scheduler is connected with an entity server, and the load scheduler deploys an agent, main bottom layer scheduling software LVS and a keepalive;
and searching target application program node information capable of providing the service type required by the service flow in an application program node registry of the zookeeper cluster according to the service type required by the service flow received by the data input port of the load scheduler.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010813794.9A CN112118291B (en) | 2020-08-13 | 2020-08-13 | Load balancing system and method for service flow |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010813794.9A CN112118291B (en) | 2020-08-13 | 2020-08-13 | Load balancing system and method for service flow |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112118291A CN112118291A (en) | 2020-12-22 |
| CN112118291B true CN112118291B (en) | 2022-11-18 |
Family
ID=73803946
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010813794.9A Active CN112118291B (en) | 2020-08-13 | 2020-08-13 | Load balancing system and method for service flow |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112118291B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113791902A (en) * | 2021-08-31 | 2021-12-14 | 北京达佳互联信息技术有限公司 | Data processing method and device, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105159767A (en) * | 2015-09-06 | 2015-12-16 | 北京京东尚科信息技术有限公司 | Method and device for realizing distributed scheduling on the basis of zookeeper |
| CN106657354A (en) * | 2016-12-29 | 2017-05-10 | 努比亚技术有限公司 | Load balancing device and method |
| WO2018099067A1 (en) * | 2016-11-29 | 2018-06-07 | 上海壹账通金融科技有限公司 | Distributed task scheduling method and system |
| CN108134828A (en) * | 2017-12-20 | 2018-06-08 | 金蝶软件（中国）有限公司 | Method for routing, device, computer equipment and the storage medium of service request |
| CN109451065A (en) * | 2018-12-26 | 2019-03-08 | 中电福富信息科技有限公司 | A kind of soft load balancing shunts automated system and its operation method |
-
2020
- 2020-08-13 CN CN202010813794.9A patent/CN112118291B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105159767A (en) * | 2015-09-06 | 2015-12-16 | 北京京东尚科信息技术有限公司 | Method and device for realizing distributed scheduling on the basis of zookeeper |
| WO2018099067A1 (en) * | 2016-11-29 | 2018-06-07 | 上海壹账通金融科技有限公司 | Distributed task scheduling method and system |
| CN106657354A (en) * | 2016-12-29 | 2017-05-10 | 努比亚技术有限公司 | Load balancing device and method |
| CN108134828A (en) * | 2017-12-20 | 2018-06-08 | 金蝶软件（中国）有限公司 | Method for routing, device, computer equipment and the storage medium of service request |
| CN109451065A (en) * | 2018-12-26 | 2019-03-08 | 中电福富信息科技有限公司 | A kind of soft load balancing shunts automated system and its operation method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112118291A (en) | 2020-12-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11194566B1 (en) | Decentralized, cluster-managed deployment of software updates in a multi-cluster environment | |
| US11184434B2 (en) | Top-of-rack switch replacement for hyper-converged infrastructure computing environments | |
| US11614958B2 (en) | Cost-efficient high-availability multi-single-tenant services | |
| US8387060B2 (en) | Virtual machine resource allocation group policy based on workload profile, application utilization and resource utilization | |
| JP2022520005A (en) | Patch management in a hybrid computing environment | |
| CN110417613B (en) | Distributed performance testing method, device, equipment and storage medium based on Jmeter | |
| US8108855B2 (en) | Method and apparatus for deploying a set of virtual software resource templates to a set of nodes | |
| US8893133B2 (en) | Dynamic test scheduling by ordering tasks for performance based on similarities between the tasks | |
| US8156370B2 (en) | Computer system and method of control thereof | |
| JP4964220B2 (en) | Realization of security level in virtual machine failover | |
| US9886260B2 (en) | Managing software version upgrades in a multiple computer system environment | |
| US8904159B2 (en) | Methods and systems for enabling control to a hypervisor in a cloud computing environment | |
| US20140137111A1 (en) | Host naming application programming interface | |
| CN106980529B (en) | Computer system for managing resources of baseboard management controller | |
| CN113971095A (en) | KUBERNETES application program interface in extended process | |
| JP2007183904A (en) | Event processing system, method, apparatus and program | |
| US9116860B2 (en) | Cascading failover of blade servers in a data center | |
| CN114174993A (en) | Optimizing cluster applications in a cluster infrastructure | |
| US20160147553A1 (en) | Minimizing guest operating system licensing costs in a processor based licensing model in a virtual datacenter | |
| US9032400B1 (en) | Opportunistic initiation of potentially invasive actions | |
| CN106130763A (en) | Server cluster and be applicable to the database resource group method for handover control of this cluster | |
| CN112118291B (en) | Load balancing system and method for service flow | |
| US11658868B2 (en) | Mixed mode management | |
| US11086615B2 (en) | Virtual appliance upgrades in high-availability (HA) computing clusters | |
| US10572412B1 (en) | Interruptible computing instance prioritization |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |