CN111078391A - Service request processing method, device and equipment - Google Patents
Service request processing method, device and equipment Download PDFInfo
- Publication number
- CN111078391A CN111078391A CN201811229715.9A CN201811229715A CN111078391A CN 111078391 A CN111078391 A CN 111078391A CN 201811229715 A CN201811229715 A CN 201811229715A CN 111078391 A CN111078391 A CN 111078391A
- Authority
- CN
- China
- Prior art keywords
- token
- threshold
- node
- load balancing
- node group
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements 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/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5083—Techniques for rebalancing the load in a distributed system
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)
Abstract
The application provides a service request processing method, a device and equipment, wherein the method comprises the following steps: receiving a token request sent by an application node aiming at the service request; acquiring the receiving quantity of token requests in a preset time; judging whether the receiving quantity exceeds a load balancing threshold value; and if not, sending a first token response aiming at the token request to the application node so that the application node processes the service request according to the first token response. By the technical scheme, the access flow can be uniformly distributed to each application node as far as possible, and the overall processing capacity of a large-scale distributed system is guaranteed.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, and a device for processing a service request.
Background
In a large-scale distributed system, a plurality of application nodes and load balancing equipment are included, and the application nodes are used for providing the same service. After receiving the service request, the load balancing device balances the service request to the application nodes, and after receiving the service request, the application nodes can process the service request.
The application node may also be throttled because of its limited service capabilities. For example, the configured current limit threshold is 100 per second, and when the number of service requests received by the application node in 1 second reaches 100, new service requests are not processed, so that the processing performance of the application node is ensured.
Obviously, if the large-scale distributed system includes two application nodes, the large-scale distributed system processes a maximum of 200 service requests per second. However, if the load balancing device allocates the service requests to the application nodes, there is no even allocation, for example, 80 service requests are allocated to the application node 1, and 120 service requests are allocated to the application node 2, the application node 1 processes 80 service requests, the application node 2 processes 100 service requests, that is, the large-scale distributed system processes 180 service requests altogether, and 20 service requests are discarded by the application node 2, so that the processing capability of the large-scale distributed system is reduced in the above manner.
Disclosure of Invention
The application provides a service request processing method, which comprises the following steps:
receiving a token request sent by an application node aiming at the service request;
acquiring the receiving quantity of token requests in a preset time;
judging whether the receiving quantity exceeds a load balancing threshold value; wherein the load balancing threshold comprises an upper threshold configured for at least one application node in a node group;
and if not, sending a first token response aiming at the token request to the application node so that the application node processes the service request according to the first token response.
The application provides a service request processing method, which comprises the following steps:
receiving threshold value change information sent by a coordination server, and adjusting the current load balancing threshold value of the node group according to the threshold value change information to obtain an adjusted load balancing threshold value; wherein the adjusted load balancing threshold comprises an upper threshold configured for at least one application node in a node group;
receiving a token request sent by an application node aiming at the service request;
and responding to the token request according to the adjusted load balancing threshold.
The application provides a service request processing method, which comprises the following steps:
acquiring threshold change information of a node group; the application nodes in the distributed system are divided into a plurality of node groups, and different node groups correspond to the same or different token servers;
and sending the threshold change information to a token server corresponding to the node group, so that the token server adjusts the current load balancing threshold of the node group according to the threshold change information to obtain an adjusted load balancing threshold, and responding to a token request according to the adjusted load balancing threshold.
The application provides a service request processing method, which comprises the following steps:
dividing application nodes in a distributed system into a plurality of node groups, wherein the node groups correspond to a plurality of regional servers, and different node groups correspond to the same or different regional servers;
and processing the service request through coordination among the plurality of regional servers.
The application provides a service request processing method, which comprises the following steps:
receiving a service request;
sending a token request for the service request to a token server;
if a first token response returned by the token server for the token request is received, processing the service request according to the first token response; wherein the first token response is sent by the token server when the receiving number of token requests in a preset time does not exceed a load balancing threshold value, and the load balancing threshold value comprises an upper threshold value configured for application nodes in a node group.
The application provides a service request processing device, the device includes:
the receiving module is used for receiving a token request sent by an application node aiming at the service request;
the acquisition module is used for acquiring the receiving number of the token requests in the preset time;
the judging module is used for judging whether the receiving quantity exceeds a load balancing threshold value or not; wherein the load balancing threshold comprises an upper threshold configured for at least one application node in a node group;
and the sending module is used for sending a first token response aiming at the token request to the application node when the judgment result is negative so that the application node processes the service request according to the first token response.
The application provides a service request processing device, the device includes:
the acquisition module is used for acquiring threshold change information of the node group; the application nodes in the distributed system are divided into a plurality of node groups, and different node groups correspond to the same or different token servers;
and the sending module is used for sending the threshold change information to the token server corresponding to the node group, so that the token server adjusts the current load balancing threshold of the node group according to the threshold change information to obtain the adjusted load balancing threshold, and responds to the token request according to the adjusted load balancing threshold.
The present application provides a token server, comprising:
a processor and a machine-readable storage medium having stored thereon a plurality of computer instructions, the processor when executing the computer instructions performs:
receiving a token request sent by an application node aiming at the service request;
acquiring the receiving quantity of token requests in a preset time;
judging whether the receiving quantity exceeds a load balancing threshold value; wherein the load balancing threshold comprises an upper threshold configured for at least one application node in a node group;
and if not, sending a first token response aiming at the token request to the application node so that the application node processes the service request according to the first token response.
The present application provides a coordination server, comprising:
a processor and a machine-readable storage medium having stored thereon a plurality of computer instructions, the processor when executing the computer instructions performs:
acquiring threshold change information of a node group; the application nodes in the distributed system are divided into a plurality of node groups, and different node groups correspond to the same or different token servers;
and sending the threshold change information to a token server corresponding to the node group, so that the token server adjusts the current load balancing threshold of the node group according to the threshold change information to obtain an adjusted load balancing threshold, and responding to a token request according to the adjusted load balancing threshold.
Based on the technical scheme, in the embodiment of the application, the access flow of each application node can be limited from the dimension of the large-scale distributed system, and the access flow is not limited from the dimension of a single application node, so that the access flow is uniformly distributed to each application node as much as possible, the overall processing capacity of the large-scale distributed system is ensured, and the processing resources of the large-scale distributed system are reasonably utilized. For example, the large-scale distributed system includes two application nodes, the large-scale distributed system processes 200 service requests at most per second, and if the load balancing device does not distribute the service requests to the application nodes evenly, for example, 80 service requests are distributed to the application node 1, and 120 service requests are distributed to the application node 2, the application node 1 processes 80 service requests, and the application node 2 processes 120 service requests, that is, the large-scale distributed system processes 200 service requests in total, thereby ensuring the processing capability of the large-scale distributed system.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments of the present application or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings of the embodiments of the present application.
Fig. 1 is a flowchart of a service request processing method according to an embodiment of the present application;
fig. 2 is a flowchart of a service request processing method according to another embodiment of the present application;
fig. 3 is a flowchart of a service request processing method according to another embodiment of the present application;
fig. 4 is a flowchart of a service request processing method according to another embodiment of the present application;
FIG. 5A is a schematic diagram of an application scenario in an embodiment of the present application;
fig. 5B is a flowchart of a service request processing method according to an embodiment of the present application;
FIG. 6A is a schematic diagram of an application scenario in another embodiment of the present application;
FIG. 6B is a schematic diagram illustrating adjustment of load balancing thresholds according to an embodiment of the present application;
fig. 7 is a block diagram of a service request processing apparatus according to an embodiment of the present application;
fig. 8 is a block diagram of a service request processing apparatus according to another embodiment of the present application;
fig. 9 is a block diagram of a service request processing device according to another embodiment of the present application.
Detailed Description
The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the 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 herein is meant to encompass any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in the embodiments of the present application to describe various information, the information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. Depending on the context, moreover, the word "if" as used may be interpreted as "at … …" or "when … …" or "in response to a determination".
An embodiment of the present application provides a service request processing method, which may be applied to a token server (e.g., token server), and as shown in fig. 1, is a flowchart of the method, where the method may include:
If not, step 104 may be performed; if so, step 105 may be performed.
In the above embodiment, the token server may correspond to a node group, and the load balancing threshold may include an upper threshold configured for at least one application node in the node group.
In one example, all application nodes in the distributed system may be added to the node group; alternatively, part of the application nodes in the distributed system may be added to the node group.
In one example, the load balancing threshold may be determined according to a current limiting threshold of an application node in the node group; or, the threshold change information sent by the coordination server may be received, and the current load balancing threshold of the node group may be adjusted according to the threshold change information, so as to obtain the adjusted load balancing threshold.
Further, before receiving the threshold change information sent by the coordination server, threshold parameter information corresponding to the application node in the node group may also be obtained, and the threshold parameter information is sent to the coordination server, so that the coordination server determines the threshold change information corresponding to the node group according to the threshold parameter information.
In an example, the execution sequence is only an example given for convenience of description, and in practical applications, the execution sequence between steps may also be changed, and the execution sequence is not limited. In other embodiments, the steps of the respective methods are not necessarily performed in the order shown and described herein, and the methods may include more or less steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.
Based on the technical scheme, in the embodiment of the application, the access flow of each application node can be limited from the dimension of the large-scale distributed system, and the access flow is not limited from the dimension of a single application node any more, so that the access flow can be uniformly distributed to each application node as much as possible, the overall processing capacity of the large-scale distributed system is ensured, and the processing resources of the large-scale distributed system are reasonably utilized.
An embodiment of the present application provides a service request processing method, which may be applied to a token server (e.g., token server), and as shown in fig. 2, is a flow diagram of the method, where the method may include:
Specifically, the receiving number of the token requests in the preset time, that is, the total number of the token requests received by the token server in the preset time may be obtained, where the token requests may be sent by a plurality of application nodes; then, it can be judged whether the received number exceeds the adjusted load balancing threshold; if not, sending a first token response aiming at the token request to the application node so that the application node processes the service request according to the first token response; if so, a second token response to the token request may be sent to the application node, such that the application node discards the traffic request according to the second token response.
In an example, the execution sequence is only an example given for convenience of description, and in practical applications, the execution sequence between steps may also be changed, and the execution sequence is not limited. In other embodiments, the steps of the respective methods are not necessarily performed in the order shown and described herein, and the methods may include more or less steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.
Based on the technical scheme, in the embodiment of the application, the access flow of each application node can be limited from the dimension of the large-scale distributed system, and the access flow is not limited from the dimension of a single application node any more, so that the access flow is distributed to each application node as uniformly as possible, the overall processing capacity of the large-scale distributed system can be ensured, and the processing resources of the large-scale distributed system can be reasonably utilized.
An embodiment of the present application provides a service request processing method, which may be applied to a coordination server (e.g., a global coordinator), and referring to fig. 3, the method is a flowchart of the method, and the method may include:
In one example, threshold parameter information corresponding to the application node in the node group may be obtained from the token server, and the threshold change information corresponding to the node group may be determined according to the threshold parameter information.
Determining the threshold change information corresponding to the node group according to the threshold parameter information may include: determining the load balancing degree according to the threshold parameter information; and if the load balancing degree is greater than the balancing threshold, selecting a target node group from all the node groups, and determining threshold change information corresponding to the target node group.
Determining the load balancing degree according to the threshold parameter information may include: if the threshold parameter information includes the token request quantity and the token supply quantity, determining a token supply proportion of the node group according to the token request quantity and the token supply quantity (i.e. dividing the token request quantity by the token supply quantity); the degree of load balancing may then be determined based on the token supply proportions for each node group.
Wherein, selecting the target node group from all the node groups may include: sorting each node group according to the size sequence (such as the sequence from small to large or the sequence from large to small) of the token supply proportion of each node group; then, based on the sorting result, a node group with the smallest token supply ratio and a node group with the largest token supply ratio may be selected, and the selected node group may be determined as the target node group.
Determining the threshold change information corresponding to the target node group may include: determining that the threshold change information of the node group with the smallest token supply proportion is the reduction load balancing threshold; the threshold change information for the node group that determines the largest proportion of token supply is to increase the load balancing threshold. For example, the threshold change information of the node group with the smallest token supply ratio may be obtained by decreasing the load balancing threshold by 5, and the threshold change information of the node group with the largest token supply ratio may be obtained by increasing the load balancing threshold by 5.
In an example, the execution sequence is only an example given for convenience of description, and in practical applications, the execution sequence between steps may also be changed, and the execution sequence is not limited. In other embodiments, the steps of the respective methods are not necessarily performed in the order shown and described herein, and the methods may include more or less steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.
Based on the technical scheme, in the embodiment of the application, the access flow of each application node can be limited from the dimension of the large-scale distributed system, and the access flow is not limited from the dimension of a single application node any more, so that the access flow is distributed to each application node as uniformly as possible, the overall processing capacity of the large-scale distributed system can be ensured, and the processing resources of the large-scale distributed system can be reasonably utilized.
An embodiment of the present application provides a service request processing method, which may be applied to an application node (e.g., an application server), and as shown in fig. 4, is a flowchart of the method, where the method may include:
In another example, if a second token response returned by the token server for the token request is received, the service request is discarded according to the second token response; and the second token response is sent by the token server when the receiving number of the token requests in the preset time exceeds a load balancing threshold value.
In the above embodiment, the token server may correspond to a node group, and the load balancing threshold may include an upper threshold configured for at least one application node in the node group.
In an example, before step 402, the receiving number of the service requests in the preset time may also be obtained, that is, the total number of the service requests received by the application node in the preset time; if the receiving quantity reaches the maximum service capacity, the service request can be directly discarded, that is, the service request is subjected to the flow limiting processing, and the step 402 is not executed; if the received number does not reach the maximum service capability, step 402 is executed.
In an example, the execution sequence is only an example given for convenience of description, and in practical applications, the execution sequence between steps may also be changed, and the execution sequence is not limited. In other embodiments, the steps of the respective methods are not necessarily performed in the order shown and described herein, and the methods may include more or less steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.
Based on the technical scheme, in the embodiment of the application, the access flow of each application node can be limited from the dimension of the large-scale distributed system, and the access flow is not limited from the dimension of a single application node any more, so that the access flow is distributed to each application node as uniformly as possible, the overall processing capacity of the large-scale distributed system can be ensured, and the processing resources of the large-scale distributed system can be reasonably utilized.
The embodiment of the application provides a service request processing method, which may include: dividing application nodes in a distributed system into a plurality of node groups, wherein the node groups can correspond to a plurality of regional servers, and different node groups can correspond to the same or different regional servers, for example, each node group corresponds to one regional server; and processing the service request through coordination among the plurality of regional servers.
In one example, the zone server may be the token server in the above embodiments; the processing of the service request through coordination among the plurality of regional servers may include: for the area server corresponding to each node group, the token request sent by the application node in the node group may be responded by the area server, so that the application node processes the service request according to the response result of the token request, and specific processing procedures may refer to the above embodiments, and are not repeated herein.
The service request processing method is described in detail below with reference to specific application scenarios.
Referring to fig. 5A, which is a schematic view of an application scenario of this embodiment, a distributed system may include a load balancing device, a plurality of application nodes (which may also be referred to as application servers or application instances, and these application nodes are used to provide the same service), and a token server (such as a token server). In the application scenario, the application nodes may be added to the same node group a, and the token server may correspond to the node group a.
In one example, the service capability of the application node is limited, e.g., the maximum service capability is 150 per second, which means that the application node processes a maximum of 150 traffic requests per second, but the application node does not process 150 traffic requests per second but limits the flow of the application node in order to ensure the processing performance of the application node. If the current limit threshold is configured to be 100 per second, when the number of the service requests received by the application node in 1 second reaches 100, the new service requests are not processed, so that the processing performance of the application node is ensured.
However, when the current limiting threshold is configured for the application node, there may be a problem that the processing capacity of the distributed system is reduced. For example, if the load balancing device allocates the service requests to the application node, there is no average allocation, for example, 80 service requests are allocated to the application node 1, and 120 service requests are allocated to the application node 2, the application node 1 processes 80 service requests, the application node 2 processes only 100 service requests, that is, the distributed system processes 180 service requests altogether, and 20 service requests are discarded by the application node 2.
In view of the above discovery, in this embodiment, the application node is no longer throttled by using the throttling threshold, but a load balancing threshold is configured in the token server, and the application node is throttled by using the load balancing threshold. The load balancing threshold is an upper threshold configured for all application nodes in the node group a, and may be determined according to the current limiting threshold of the application nodes in the node group a. For example, the node group a includes an application node 1 and an application node 2, the current limiting threshold of the application node 1 is 100 per second, and the current limiting threshold of the application node 2 is 100 per second, so that the load balancing threshold may be 200 per second. Of course, the above is only an example of determining the load balancing threshold, and the load balancing threshold is not limited thereto, for example, the load balancing threshold may be other values.
In the application scenario, referring to fig. 5B, a flowchart of a service request processing method is shown.
Specifically, after receiving the service request, the load balancing device may balance the service request to a plurality of application nodes, so that each application node may receive the service request.
In step 502, the application node obtains the received number of service requests within a preset time, that is, the total number of service requests received by the application node within the preset time (which may be configured empirically, for example, 1 second).
Specifically, when receiving a service request, the application node determines the receiving time of the service request as the current time, and slides forward for a preset time from the current time to obtain the starting time, so that the application node can count the total number of the received service requests in the time period from the starting time to the current time.
In step 503, the application node determines whether the received number reaches a maximum service capacity, such as 150 per second.
If so, step 504 may be performed, and if not, step 505 may be performed.
In step 504, the application node directly discards the service request, i.e. performs a flow limiting process on the service request.
In step 505, the application node sends a token request for the service request to the token server.
The token server receives a token request sent by the application node for the service request, step 506.
In step 507, the token server obtains the receiving number of token requests within a preset time (which may be configured empirically, such as 1 second, etc.), that is, the total number of token requests received by the token server within the preset time, where the token requests may be token requests sent by all application nodes in the node group a.
Specifically, when receiving a token request, the token server determines the receiving time of the token request as the current time, and slides forward for a preset time from the current time to obtain the starting time, so that the token server may count the total number of received token requests within the time period from the starting time to the current time, where the token requests may be token requests sent by all application nodes in the node group a.
At step 508, the token server determines whether the received number exceeds a load balancing threshold, such as 200 per second. If not, step 509 may be performed; if so, step 511 may be performed.
The token server sends 509 a first token response to the application node for the token request.
In step 510, if the application node receives the first token response, the service request is processed according to the first token response, and the processing procedure is not limited and may be related to an actual service.
The token server sends a second token response to the application node for the token request, step 511.
Based on the technical scheme, in the embodiment of the application, the access flow of each application node can be limited from the dimension of the large-scale distributed system, and the access flow is not limited from the dimension of a single application node any more, so that the access flow is distributed to each application node as uniformly as possible, the overall processing capacity of the large-scale distributed system can be ensured, and the processing resources of the large-scale distributed system can be reasonably utilized.
Referring to fig. 6A, as an application scenario diagram of this embodiment, a distributed system may include a load balancing device, a plurality of application nodes (such as an application server or an application instance), a token server (such as a token server), and a coordination server (such as a global coordinator), in this application scenario, the application nodes 1 to 6 may be added to a node group a, the token server 1 may correspond to the node group a, the application nodes 7 to 12 may be added to a node group B, and the token server 2 may correspond to the node group B.
For example, all application nodes of the same machine room may be added to the same node group, and application nodes of different machine rooms may be added to different node groups. Of course, other strategies may also be adopted to add the application node to a certain node group, and the division manner of the node group is not limited.
The number of application nodes in different node groups may be the same or different.
In one example, a load balancing threshold may be configured at the token server and utilized to throttle the application nodes. The load balancing threshold is a threshold upper limit configured for all application nodes in the node group, and is determined according to the current limiting threshold of the application nodes in the node group.
For example, the node group a includes application nodes 1 to 6, and the current limiting threshold of each application node is 100 per second, then the load balancing threshold configured at the token server 1 may be 600 per second. Node group B includes application nodes 7-12, and the current limit threshold of each application node is 120 per second, then the load balancing threshold configured at the token server 2 may be 720 per second. Of course, the above is only an example of determining the load balancing threshold, and the load balancing threshold is not limited thereto, for example, the load balancing threshold may be other values.
In an example, after the token server configures the load balancing threshold, the load balancing threshold may be further dynamically adjusted, as shown in fig. 6B, which is a schematic diagram of dynamically adjusting the load balancing threshold.
In one example, the threshold parameter information may include, but is not limited to, one or any combination of the following: number of token requests, number of token supplies, load information, etc., without limitation to this threshold parameter information.
The number of token requests may be the total number of token requests sent by all application nodes in the node group within a preset time (e.g., 1 second), that is, the total number of token requests received by the token server within the preset time. For example, if each of the application nodes 1 to 4 sends 100 token requests within a preset time, and each of the application nodes 5 and 6 sends 120 token requests within a preset time, the number of token requests may be 640 token requests. It should be noted that this token request number may be greater than the load balancing threshold of the token server 1, where the token request number is the total number of token requests sent by all application nodes within a preset time, and is the sum of the token request success number and the token request failure number.
The token supply quantity may be a load balancing degree corresponding to the node group, such as 600.
The load information may include, but is not limited to: each application node CPU (central processing Unit) usage, memory usage, CPU load, network latency, etc. in a node group. For example, the load information may include, but is not limited to, the CPU usage of the application nodes 1-6.
In step 602, the token server sends the threshold parameter information to the coordinating server.
For example, the coordinating server may obtain threshold parameter information a from token server 1 and threshold parameter information B from token server 2. Then, the coordination server may determine the load balancing degree according to the threshold parameter information a and the threshold parameter information B, and a determination process of the load balancing degree will be described below.
In one example, the coordination server determines the load balancing level according to the threshold parameter information, which may include but is not limited to: if the threshold parameter information includes a token request quantity and a token supply quantity, the coordination server may determine a token supply ratio for the node group based on the token request quantity and the token supply quantity, e.g., the token supply ratio may be the token request quantity divided by the token supply quantity. The coordination server may then determine a degree of load balancing based on the token supply proportions for each node group.
The coordination server determines the load balancing degree according to the token supply ratio of each node group, which may include but is not limited to: and counting the number of first node groups with the token supply ratio larger than a first threshold value, and counting the number of second node groups with the token supply ratio smaller than a second threshold value. Then, if the number of the first node groups is less than or equal to the number of the second node groups, the load balancing degree may be the number of the first node groups; if the number of the first node groups is greater than the number of the second node groups, the load balancing degree may be the number of the second node groups.
Wherein the first threshold may be 1+ R and the second threshold may be 1-S; r may be a constant greater than or equal to 0 and less than 1, and may be configured empirically; s may be a constant greater than or equal to 0 and less than 1, and may be configured empirically; by adjusting the values of R and S, the sensitivity of load fluctuations can be controlled.
For example, in the threshold parameter information a, the token request number is 640, the token supply number is 600, and the token supply ratio of the node group a is 1.07, and in the threshold parameter information B, the token request number is 560, and the token supply number is 600, and the token supply ratio of the node group B is 0.93. Assuming that the token supply ratio of 1.07 is greater than the first threshold and the token supply ratio of 0.93 is less than the second threshold, the first node group number is 1 and the second node group number is 1, and thus, the load balancing degree may be the first node group number of 1.
Of course, the above manner is only an example of determining the load balancing degree, and is not limited thereto, for example, the load balancing degree may also be determined according to a CPU usage rate, a memory usage rate, a CPU load, a network delay, and the like.
In one example, the coordinating server selects a target node group from all node groups, which may include, but is not limited to: the coordination server sorts each node group according to the size sequence of the token supply proportion of each node group (for example, the sequence of the token supply proportion from small to large, or the sequence of the token supply proportion from large to small); then, based on the sorting result, the coordinating server may select a node group with the smallest token supply ratio and a node group with the largest token supply ratio, and determine the selected node group as the target node group.
For example, the coordinating server determines the node group with the largest token supply ratio (e.g., node group a) as the target node group and determines the node group with the smallest token supply ratio (e.g., node group B) as the target node group.
At step 606, the coordination server determines threshold change information corresponding to the target node group. Specifically, the coordination server determines that the threshold change information of the node group with the smallest token supply ratio is to lower the load balancing threshold, and determines that the threshold change information of the node group with the largest token supply ratio is to increase the load balancing threshold.
For example, the threshold change information of the node group B with the smallest token supply ratio may be obtained by decreasing the load balancing threshold by 10, 20, or 40, which is not limited to this, and then 40 are taken as an example; the threshold change information of the node group a with the largest token supply ratio may be obtained by increasing the load balancing threshold by 10, 20, or 40, which is not limited herein. It should be noted that the number of the decrease of the load balancing threshold of the node group B may be the same as the number of the increase of the load balancing threshold of the node group a, which is not limited herein.
For example, the coordinating server may send the threshold change information of node group a to token server 1 corresponding to node group a and send the threshold change information of node group B to token server 2 corresponding to node group B.
For example, the token server 1 adjusts the current load balancing thresholds (for example, 600) of the node group a according to the threshold change information (for example, 10 load balancing thresholds are increased), so as to obtain adjusted load balancing thresholds, that is, the adjusted load balancing thresholds are 610. The token server 2 adjusts the current load balancing thresholds (e.g., 600) of the node group B according to the threshold change information (e.g., reduces the load balancing thresholds by 10), to obtain adjusted load balancing thresholds, that is, 590 adjusted load balancing thresholds.
After the load balancing threshold is dynamically adjusted, the flow shown in fig. 6B is executed again in the next cycle.
Based on the load balancing threshold determined in the above manner, the processing flow shown in fig. 5B may be adopted to implement the service request processing method, and specific implementation processes refer to the above embodiments and are not repeated herein.
Based on the same application concept as the method described above, an embodiment of the present application further provides a service request processing apparatus, as shown in fig. 7, which is a structural diagram of the apparatus, and the apparatus may include:
a receiving module 71, configured to receive a token request sent by an application node for a service request;
an obtaining module 72, configured to obtain a receiving number of token requests within a preset time;
a determining module 73, configured to determine whether the received number exceeds a load balancing threshold; wherein the load balancing threshold comprises an upper threshold configured for at least one application node in a node group;
and a sending module 74, configured to send a first token response to the token request to the application node when the determination result is negative, so that the application node processes the service request according to the first token response.
The sending module 74 is further configured to send a second token response to the token request to the application node when the determination result is yes, so that the application node discards the service request according to the second token response.
An obtaining module 72, configured to obtain threshold parameter information corresponding to the application nodes in the node group;
the sending module 74 is further configured to send the threshold parameter information to a coordination server, so that the coordination server determines, according to the threshold parameter information, threshold change information corresponding to the node group;
the receiving module 71 is further configured to receive threshold change information sent by the coordination server;
the device further comprises (not shown in the figures): and the adjusting module is used for adjusting the current load balancing threshold of the node group according to the threshold changing information to obtain the adjusted load balancing threshold.
Based on the same concept as the method described above, the present embodiment further provides a token server, including: a processor and a machine-readable storage medium; the machine-readable storage medium has stored thereon a plurality of computer instructions, which when executed by the processor, perform the following:
receiving a token request sent by an application node aiming at the service request;
acquiring the receiving quantity of token requests in a preset time;
judging whether the receiving quantity exceeds a load balancing threshold value; wherein the load balancing threshold comprises an upper threshold configured for at least one application node in a node group;
and if not, sending a first token response aiming at the token request to the application node so that the application node processes the service request according to the first token response.
The present embodiments also provide a machine-readable storage medium having stored thereon computer instructions that, when executed, perform the following:
receiving a token request sent by an application node aiming at the service request;
acquiring the receiving quantity of token requests in a preset time;
judging whether the receiving quantity exceeds a load balancing threshold value; wherein the load balancing threshold comprises an upper threshold configured for at least one application node in a node group;
and if not, sending a first token response aiming at the token request to the application node so that the application node processes the service request according to the first token response.
Based on the same application concept as the method described above, an embodiment of the present application further provides a service request processing apparatus, as shown in fig. 8, which is a structural diagram of the apparatus, and the apparatus may include:
an obtaining module 81, configured to obtain threshold change information of the node group; the application nodes in the distributed system are divided into a plurality of node groups, and different node groups correspond to the same or different token servers;
a sending module 82, configured to send the threshold change information to the token server corresponding to the node group, so that the token server adjusts the current load balancing threshold of the node group according to the threshold change information, to obtain an adjusted load balancing threshold, and responds to the token request according to the adjusted load balancing threshold.
The obtaining module 81 is specifically configured to, when obtaining the threshold change information of the node group:
acquiring threshold parameter information corresponding to application nodes in a node group from a token server;
determining threshold value change information corresponding to the node group according to the threshold value parameter information; the obtaining module 81 is specifically configured to, when determining the threshold change information corresponding to the node group according to the threshold parameter information: determining the load balancing degree according to the threshold parameter information; if the load balancing degree is larger than a balancing threshold value, selecting a target node group from all the node groups; and determining threshold change information corresponding to the target node group.
Based on the same concept as the method described above, this embodiment further provides a coordination server, where the coordination server includes: a processor and a machine-readable storage medium; the machine-readable storage medium has stored thereon a plurality of computer instructions, which when executed by the processor, perform the following:
acquiring threshold change information of a node group; the application nodes in the distributed system are divided into a plurality of node groups, and different node groups correspond to the same or different token servers;
and sending the threshold change information to a token server corresponding to the node group, so that the token server adjusts the current load balancing threshold of the node group according to the threshold change information to obtain an adjusted load balancing threshold, and responding to a token request according to the adjusted load balancing threshold.
The present embodiments also provide a machine-readable storage medium having stored thereon computer instructions that, when executed, perform the following:
acquiring threshold change information of a node group; the application nodes in the distributed system are divided into a plurality of node groups, and different node groups correspond to the same or different token servers;
and sending the threshold change information to a token server corresponding to the node group, so that the token server adjusts the current load balancing threshold of the node group according to the threshold change information to obtain an adjusted load balancing threshold, and responding to a token request according to the adjusted load balancing threshold.
Based on the same application concept as the method described above, an embodiment of the present application further provides a service request processing apparatus, as shown in fig. 9, which is a structural diagram of the apparatus, and the apparatus may include:
a receiving module 91, configured to receive a service request;
a sending module 92, configured to send a token request for the service request to a token server;
a processing module 93, configured to, if a first token response returned by the token server for the token request is received, process the service request according to the first token response; the first token response is sent by the token server when the receiving number of token requests in a preset time does not exceed a load balancing threshold value, wherein the load balancing threshold value comprises an upper threshold value configured for application nodes in a node group.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Furthermore, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (22)
1. A service request processing method, characterized in that the method comprises:
receiving a token request sent by an application node aiming at the service request;
acquiring the receiving quantity of token requests in a preset time;
judging whether the receiving quantity exceeds a load balancing threshold value; wherein the load balancing threshold comprises an upper threshold configured for at least one application node in a node group;
and if not, sending a first token response aiming at the token request to the application node so that the application node processes the service request according to the first token response.
2. The method of claim 1,
after determining whether the receiving number exceeds a load balancing threshold, the method further includes:
and if so, sending a second token response aiming at the token request to the application node so as to enable the application node to discard the service request according to the second token response.
3. The method of claim 1, further comprising:
adding all application nodes in the distributed system to the node group; alternatively, the first and second electrodes may be,
and adding part of application nodes in the distributed system to the node group.
4. The method according to claim 1 or 3, characterized in that the method further comprises:
determining the load balancing threshold according to the current limiting threshold of the application nodes in the node group; alternatively, the first and second electrodes may be,
and receiving threshold change information sent by the coordination server, and adjusting the current load balancing threshold of the node group according to the threshold change information to obtain the adjusted load balancing threshold.
5. The method of claim 4,
before the receiving the threshold change information sent by the coordination server, the method further includes:
acquiring threshold parameter information corresponding to application nodes in the node group;
and sending the threshold parameter information to the coordination server so that the coordination server determines threshold change information corresponding to the node group according to the threshold parameter information.
6. A service request processing method, characterized in that the method comprises:
receiving threshold value change information sent by a coordination server, and adjusting the current load balancing threshold value of the node group according to the threshold value change information to obtain an adjusted load balancing threshold value; wherein the adjusted load balancing threshold comprises an upper threshold configured for at least one application node in a node group;
receiving a token request sent by an application node aiming at the service request;
and responding to the token request according to the adjusted load balancing threshold.
7. The method of claim 6,
the responding to the token request according to the adjusted load balancing threshold includes:
acquiring the receiving quantity of token requests in a preset time;
judging whether the receiving quantity exceeds the adjusted load balancing threshold value;
if not, sending a first token response aiming at the token request to the application node so that the application node processes the service request according to the first token response;
and if so, sending a second token response aiming at the token request to the application node so as to enable the application node to discard the service request according to the second token response.
8. A service request processing method, characterized in that the method comprises:
acquiring threshold change information of a node group; the application nodes in the distributed system are divided into a plurality of node groups, and different node groups correspond to the same or different token servers;
and sending the threshold change information to a token server corresponding to the node group, so that the token server adjusts the current load balancing threshold of the node group according to the threshold change information to obtain an adjusted load balancing threshold, and responding to a token request according to the adjusted load balancing threshold.
9. The method of claim 8,
the obtaining of the threshold change information of the node group includes:
acquiring threshold parameter information corresponding to application nodes in a node group from a token server;
and determining threshold change information corresponding to the node group according to the threshold parameter information.
10. The method of claim 9,
the determining, according to the threshold parameter information, threshold change information corresponding to a node group includes:
determining the load balancing degree according to the threshold parameter information;
if the load balancing degree is larger than a balancing threshold value, selecting a target node group from all the node groups;
and determining threshold change information corresponding to the target node group.
11. The method of claim 10,
the determining the load balancing degree according to the threshold parameter information includes:
if the threshold parameter information comprises token request quantity and token supply quantity, determining the token supply proportion of the node group according to the token request quantity and the token supply quantity;
and determining the load balancing degree according to the token supply proportion of each node group.
12. The method of claim 11,
the selecting a target node group from all node groups includes:
sequencing each node group according to the sequence of the token supply proportion of each node group;
and selecting the node group with the smallest token supply proportion and the node group with the largest token supply proportion based on the sorting result, and determining the selected node group as the target node group.
13. The method of claim 12,
the determining the threshold change information corresponding to the target node group includes:
determining that the threshold change information of the node group with the smallest token supply proportion is the reduction load balancing threshold;
the threshold change information for the node group that determines the largest proportion of token supply is to increase the load balancing threshold.
14. A service request processing method, characterized in that the method comprises:
dividing application nodes in a distributed system into a plurality of node groups, wherein the node groups correspond to a plurality of regional servers, and different node groups correspond to the same or different regional servers;
and processing the service request through coordination among the plurality of regional servers.
15. A service request processing method, characterized in that the method comprises:
receiving a service request;
sending a token request for the service request to a token server;
if a first token response returned by the token server for the token request is received, processing the service request according to the first token response; wherein the first token response is sent by the token server when the receiving number of token requests in a preset time does not exceed a load balancing threshold value, and the load balancing threshold value comprises an upper threshold value configured for application nodes in a node group.
16. A service request processing apparatus, characterized in that the apparatus comprises:
the receiving module is used for receiving a token request sent by an application node aiming at the service request;
the acquisition module is used for acquiring the receiving number of the token requests in the preset time;
the judging module is used for judging whether the receiving quantity exceeds a load balancing threshold value or not; wherein the load balancing threshold comprises an upper threshold configured for at least one application node in a node group;
and the sending module is used for sending a first token response aiming at the token request to the application node when the judgment result is negative so that the application node processes the service request according to the first token response.
17. The apparatus of claim 16,
and the sending module is further configured to send a second token response to the token request to the application node when the determination result is yes, so that the application node discards the service request according to the second token response.
18. The apparatus of claim 16,
the obtaining module is further configured to obtain threshold parameter information corresponding to the application nodes in the node group;
the sending module is further configured to send the threshold parameter information to a coordination server, so that the coordination server determines, according to the threshold parameter information, threshold change information corresponding to the node group;
the receiving module is further configured to receive threshold change information sent by the coordination server;
the device further comprises: and the adjusting module is used for adjusting the current load balancing threshold of the node group according to the threshold changing information to obtain the adjusted load balancing threshold.
19. A service request processing apparatus, characterized in that the apparatus comprises:
the acquisition module is used for acquiring threshold change information of the node group; the application nodes in the distributed system are divided into a plurality of node groups, and different node groups correspond to the same or different token servers;
and the sending module is used for sending the threshold change information to the token server corresponding to the node group, so that the token server adjusts the current load balancing threshold of the node group according to the threshold change information to obtain the adjusted load balancing threshold, and responds to the token request according to the adjusted load balancing threshold.
20. The apparatus of claim 19,
the obtaining module is specifically configured to, when obtaining the threshold change information of the node group:
acquiring threshold parameter information corresponding to application nodes in a node group from a token server;
determining threshold value change information corresponding to the node group according to the threshold value parameter information; the obtaining module is specifically configured to, when determining, according to the threshold parameter information, threshold change information corresponding to a node group: determining the load balancing degree according to the threshold parameter information; if the load balancing degree is larger than a balancing threshold value, selecting a target node group from all the node groups; and determining threshold change information corresponding to the target node group.
21. A token server, the token server comprising:
a processor and a machine-readable storage medium having stored thereon a plurality of computer instructions, the processor when executing the computer instructions performs:
receiving a token request sent by an application node aiming at the service request;
acquiring the receiving quantity of token requests in a preset time;
judging whether the receiving quantity exceeds a load balancing threshold value; wherein the load balancing threshold comprises an upper threshold configured for at least one application node in a node group;
and if not, sending a first token response aiming at the token request to the application node so that the application node processes the service request according to the first token response.
22. A coordination server, characterized in that the coordination server comprises:
a processor and a machine-readable storage medium having stored thereon a plurality of computer instructions, the processor when executing the computer instructions performs:
acquiring threshold change information of a node group; the application nodes in the distributed system are divided into a plurality of node groups, and different node groups correspond to the same or different token servers;
and sending the threshold change information to a token server corresponding to the node group, so that the token server adjusts the current load balancing threshold of the node group according to the threshold change information to obtain an adjusted load balancing threshold, and responding to a token request according to the adjusted load balancing threshold.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811229715.9A CN111078391A (en) | 2018-10-22 | 2018-10-22 | Service request processing method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811229715.9A CN111078391A (en) | 2018-10-22 | 2018-10-22 | Service request processing method, device and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111078391A true CN111078391A (en) | 2020-04-28 |
Family
ID=70309761
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811229715.9A Pending CN111078391A (en) | 2018-10-22 | 2018-10-22 | Service request processing method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111078391A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111865722A (en) * | 2020-07-20 | 2020-10-30 | 深圳市活力天汇科技股份有限公司 | Node health state detection and processing method |
| CN111901380A (en) * | 2020-06-29 | 2020-11-06 | 浪潮电子信息产业股份有限公司 | Request processing method, device, equipment and storage medium |
| CN112312165A (en) * | 2020-10-19 | 2021-02-02 | 中移（杭州）信息技术有限公司 | Video distribution method and device and computer readable storage medium |
| CN112988389A (en) * | 2021-03-22 | 2021-06-18 | 成都卓拙科技有限公司 | Automatic scaling method and system combining load regulation and periodic regulation |
| CN114584375A (en) * | 2022-03-04 | 2022-06-03 | 深圳市技湛科技有限公司 | Security protection method and device for streaming media system, platform equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPS6249740A (en) * | 1985-08-29 | 1987-03-04 | Matsushita Electric Ind Co Ltd | Loop network control method |
| CN103763208A (en) * | 2014-01-29 | 2014-04-30 | 华为技术有限公司 | Data flow limiting method and device |
| CN103929366A (en) * | 2014-04-02 | 2014-07-16 | 华为技术有限公司 | Flow control method and device and equipment |
| CN107924338A (en) * | 2015-08-17 | 2018-04-17 | 微软技术许可有限责任公司 | Optimal storage device and workload in geographically distributed clusters system are placed and high resiliency |
| CN108494703A (en) * | 2018-03-08 | 2018-09-04 | 腾讯科技（深圳）有限公司 | A kind of access frequency control method, device and storage medium |
| CN108667744A (en) * | 2018-02-26 | 2018-10-16 | 华为技术有限公司 | Flow control methods and device |
-
2018
- 2018-10-22 CN CN201811229715.9A patent/CN111078391A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPS6249740A (en) * | 1985-08-29 | 1987-03-04 | Matsushita Electric Ind Co Ltd | Loop network control method |
| CN103763208A (en) * | 2014-01-29 | 2014-04-30 | 华为技术有限公司 | Data flow limiting method and device |
| CN103929366A (en) * | 2014-04-02 | 2014-07-16 | 华为技术有限公司 | Flow control method and device and equipment |
| CN107924338A (en) * | 2015-08-17 | 2018-04-17 | 微软技术许可有限责任公司 | Optimal storage device and workload in geographically distributed clusters system are placed and high resiliency |
| CN108667744A (en) * | 2018-02-26 | 2018-10-16 | 华为技术有限公司 | Flow control methods and device |
| CN108494703A (en) * | 2018-03-08 | 2018-09-04 | 腾讯科技（深圳）有限公司 | A kind of access frequency control method, device and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 杨明极;王鹤;赵加凤;: "基于CPU和内存利用率的负载均衡算法的研究" * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111901380A (en) * | 2020-06-29 | 2020-11-06 | 浪潮电子信息产业股份有限公司 | Request processing method, device, equipment and storage medium |
| CN111865722A (en) * | 2020-07-20 | 2020-10-30 | 深圳市活力天汇科技股份有限公司 | Node health state detection and processing method |
| CN112312165A (en) * | 2020-10-19 | 2021-02-02 | 中移（杭州）信息技术有限公司 | Video distribution method and device and computer readable storage medium |
| CN112988389A (en) * | 2021-03-22 | 2021-06-18 | 成都卓拙科技有限公司 | Automatic scaling method and system combining load regulation and periodic regulation |
| CN112988389B (en) * | 2021-03-22 | 2023-08-11 | 成都卓拙科技有限公司 | Automatic telescoping method and system combining load regulation and periodicity regulation |
| CN114584375A (en) * | 2022-03-04 | 2022-06-03 | 深圳市技湛科技有限公司 | Security protection method and device for streaming media system, platform equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111078391A (en) | Service request processing method, device and equipment | |
| CN109617986B (en) | Load balancing method and network equipment | |
| CN108268317B (en) | Resource allocation method and device | |
| US20230093389A1 (en) | Service request allocation method and apparatus, computer device, and storage medium | |
| CN107800768B (en) | Open platform control method and system | |
| CN110781006B (en) | Load balancing method, device, node and computer readable storage medium | |
| JP6224244B2 (en) | Power balancing to increase working density and improve energy efficiency | |
| US10356004B2 (en) | Software load balancer to maximize utilization | |
| US9405588B2 (en) | Cloud resource allocation system and method | |
| CN113810304A (en) | Load balancing method, device, equipment and computer storage medium | |
| CN107819797B (en) | Access request processing method and device | |
| CN111245732B (en) | Flow control method, device and equipment | |
| CN109672711B (en) | Reverse proxy server Nginx-based http request processing method and system | |
| CN104320854A (en) | Resource scheduling method and device | |
| CN111694663A (en) | Load balancing method, device and system for server cluster | |
| CN111131486A (en) | Load adjustment method and device of execution node, server and storage medium | |
| CN110233866B (en) | Load balancing method and load balancer | |
| CN110007867B (en) | Cache space allocation method, device, equipment and storage medium | |
| CN107491352B (en) | Resource scheduling method and device | |
| CN113760549A (en) | Pod deployment method and device | |
| CN108200185B (en) | Method and device for realizing load balance | |
| CN109981696B (en) | Load balancing method, device and equipment | |
| CN104270321A (en) | Network load balancing method and system | |
| JP5526748B2 (en) | Packet processing device, packet distribution device, control program, and packet distribution method | |
| US20140047454A1 (en) | Load balancing in an sap system |
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 |