CN116232884A - Proxy instance management method, device, electronic equipment and storage medium - Google Patents
Proxy instance management method, device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN116232884A CN116232884A CN202211617443.6A CN202211617443A CN116232884A CN 116232884 A CN116232884 A CN 116232884A CN 202211617443 A CN202211617443 A CN 202211617443A CN 116232884 A CN116232884 A CN 116232884A
- Authority
- CN
- China
- Prior art keywords
- proxy instance
- instance
- proxy
- service request
- load value
- 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
- 238000007726 management method Methods 0.000 title description 47
- 238000012544 monitoring process Methods 0.000 claims abstract description 85
- 238000000034 method Methods 0.000 claims abstract description 36
- 230000003321 amplification Effects 0.000 claims description 28
- 238000003199 nucleic acid amplification method Methods 0.000 claims description 28
- 230000004044 response Effects 0.000 claims description 25
- 238000004590 computer program Methods 0.000 claims description 16
- 239000002699 waste material Substances 0.000 abstract description 9
- 239000003795 chemical substances by application Substances 0.000 description 94
- 238000012545 processing Methods 0.000 description 14
- 230000008569 process Effects 0.000 description 11
- 238000010586 diagram Methods 0.000 description 8
- 230000003287 optical effect Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000003416 augmentation Effects 0.000 description 2
- 230000007423 decrease Effects 0.000 description 2
- 230000003247 decreasing effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The present disclosure relates to a method, an apparatus, an electronic device, and a storage medium for managing a proxy instance, by initially configuring the proxy instance based on preset configuration information, receiving service request monitoring data sent by a control plane proxy, where the service request monitoring data is obtained by the control plane proxy from a service interface, obtaining a load value of the proxy instance, and managing the proxy instance based on the service request monitoring data, or managing the proxy instance based on the load value of the proxy instance. According to the method and the device, the proxy instance is dynamically managed according to the service request monitoring data or the proxy instance load condition, so that the flexibility of proxy instance management is improved, and when the service on the cloud server node is increased, the proxy instance can be amplified, so that the overload of the traffic on the proxy instance is avoided, and the requirements of service request and service traffic forwarding are met; when the traffic flow on the cloud server node is reduced, the proxy instance is reduced, so that idle and waste of the processor and memory resources are avoided.
Description
Technical Field
The present disclosure relates to the field of data processing, and in particular, to a proxy instance management method, a proxy instance management device, an electronic device, and a storage medium.
Background
The data processor (Data Processing Unit, DPU) is a new generation of computing chips which are data-centric, I/O intensive, support infrastructure resource layer virtualization by adopting a software defined technology route, and have the advantages of improving the efficiency of the computing system, reducing the total ownership cost of the whole system, improving the data processing efficiency and reducing the performance loss of other computing chips.
A Service Mesh (Service Mesh) is an infrastructure layer in cloud services, focusing on achieving reliable delivery of Service requests between micro services, and providing traffic control layer operations such as Service discovery, load balancing, request routing, and rule configuration on the basis thereof. Currently, a plurality of proxy instances and application services on cloud server nodes are commonly used on a DPU to form a cloud native service grid, and enough proxy instances are deployed on the DPU to be capable of bearing all concurrent traffic on the cloud server nodes.
However, the number of deployed agent instances is static and cannot be dynamically increased or decreased with traffic demand, with the following problems: 1) When the service on the cloud server node suddenly increases, the quantity of the agent instances deployed on the DPU cannot meet the service request and service flow forwarding, so that the processor or the memory is insufficient, the processing time of a single data message is increased, the service request delay is increased, the jitter is increased, the service is unstable, or the service flow is discarded, so that a large quantity of retransmission is caused; 2) When traffic on cloud server nodes decreases, pre-deployed proxy instances are excessive, resulting in idle and wasted DPU processors, memory resources.
Disclosure of Invention
In order to solve the technical problems, the present disclosure provides a proxy instance management method, a proxy instance management device, an electronic device and a storage medium, so as to dynamically manage a proxy instance.
In a first aspect, an embodiment of the present disclosure provides a proxy instance management method, including:
initial configuration is carried out on the agent instance based on preset configuration information;
receiving service request monitoring data sent by a control plane agent, wherein the service request monitoring data is obtained by the control plane agent from a service interface;
acquiring a load value of an agent instance;
and managing the proxy instance based on the service request monitoring data or managing the proxy instance based on the load value of the proxy instance.
In some embodiments, the initially configuring the proxy instance based on the preset configuration information includes:
obtaining a corresponding relation between the proxy instance and the service request according to the preset configuration information;
determining a target service request corresponding to the proxy instance from the corresponding relation;
and establishing connection between the proxy instance and the target service request.
In some embodiments, the obtaining the load value of the proxy instance includes:
Calculating the resource occupancy rate of a central processor and a memory of the proxy instance;
and determining the load value of the proxy instance corresponding to the resource occupancy rate of the central processor and the memory of the proxy instance from the corresponding relation between the resource occupancy rate and the load value.
In some embodiments, the managing agent instances based on the service request monitoring data includes:
judging whether the service request monitoring data meets the amplification conditions of the proxy instance or not;
if the amplification conditions of the proxy instance are met, amplifying the proxy instance;
the managing the proxy instance based on the load value of the proxy instance comprises the following steps:
and amplifying or reducing the proxy instance according to the magnitude relation between the load value of the proxy instance and a plurality of thresholds.
In some embodiments, the service request monitoring data includes at least one of:
throughput data, retransmission rate, and response time;
the judging whether the service request monitoring data meets the amplification conditions of the proxy instance comprises the following steps:
if the throughput data is smaller than a preset throughput threshold, or the retransmission rate is larger than a preset retransmission rate threshold, or the response time is longer than a preset response time threshold, the amplification condition of the proxy instance is met;
If the throughput data is greater than or equal to the preset throughput threshold, the retransmission rate 5 is less than or equal to the preset retransmission rate threshold, and the response time is less than or equal to the preset threshold
And if the response time threshold is set, the amplification condition of the proxy instance is not satisfied.
In some embodiments, the amplifying or reducing the proxy instance according to the magnitude relation between the load value of the proxy instance and the plurality of thresholds includes:
if the load value of the proxy instance is smaller than or equal to a preset first load value threshold value, 0 is used for reducing the proxy instance;
if the load value of the proxy instance is greater than or equal to a preset second load value threshold, amplifying the proxy instance;
and if the load value of the proxy instance is larger than the preset first load value threshold and smaller than the preset second load value threshold, keeping the proxy instance unchanged.
5 in some embodiments, the reducing the proxy instance includes:
disconnecting the proxy instance from the service request, and recovering resources of the proxy instance;
the amplifying the agent instance comprises the following steps:
acquiring configuration information of a newly added agent instance from a service grid control plane; 0 determining the agent instance to be added according to the configuration information of the agent instance to be added
A service request for the connection;
and establishing connection between the newly added proxy instance and the service request.
In a second aspect, an embodiment of the present disclosure provides an agent instance management apparatus, including:
the configuration module is used for carrying out initial configuration on the agent instance based on preset configuration information; a receiving module for receiving service request monitoring data sent by the control plane agent, the receiving module comprising a receiving module for receiving the service request monitoring data sent by the control plane agent
The service request monitoring data is obtained by the control plane agent from the service interface;
the acquisition module is used for acquiring the load value of the proxy instance;
and the management module is used for managing the proxy instance based on the service request monitoring data or managing the proxy instance based on the load value of the proxy instance.
In a third aspect, an embodiment of the present disclosure provides an electronic device, including:
a memory;
a processor; and
a computer program;
wherein the computer program is stored in the memory and configured to be executed by the processor to implement the method according to the first or second aspect.
In a fourth aspect, embodiments of the present disclosure provide a computer-readable storage medium having stored thereon a computer program for execution by a processor to implement the method of the first aspect.
In a fifth aspect, embodiments of the present disclosure also provide a computer program product comprising a computer program or instructions which, when executed by a processor, implement a method as described in the first aspect.
According to the proxy instance management method, the device, the electronic equipment and the storage medium, the proxy instance is initially configured based on preset configuration information, service request monitoring data sent by a control plane proxy is received, the service request monitoring data are obtained from a service interface by the control plane proxy, a load value of the proxy instance is obtained, and the proxy instance is managed based on the service request monitoring data or is managed based on the load value of the proxy instance. According to the method and the device, the proxy instance is dynamically managed according to the service request monitoring data or the proxy instance load condition, so that the flexibility of proxy instance management is improved, and when the service on the cloud server node is increased, the proxy instance can be amplified, so that the overload of the traffic on the proxy instance is avoided, and the requirements of service request and service traffic forwarding are met; when the traffic flow on the cloud server node is reduced, the proxy instance is reduced, so that idle and waste of the processor and memory resources are avoided.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure.
In order to more clearly illustrate the embodiments of the present disclosure or the solutions in the prior art, the drawings that are required for the description of the embodiments or the prior art will be briefly described below, and it will be obvious to those skilled in the art that other drawings can be obtained from these drawings without inventive effort.
FIG. 1 is a flowchart of a proxy instance management method provided by an embodiment of the present disclosure;
FIG. 2 is a schematic flow chart of dynamic management of agent instances provided by an embodiment of the present disclosure;
FIG. 3 is a flowchart of a proxy instance management method provided by another embodiment of the present disclosure;
FIG. 4 is a flowchart of a proxy instance management method provided by another embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of an agent instance management device according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the disclosure.
Detailed Description
In order that the above objects, features and advantages of the present disclosure may be more clearly understood, a further description of aspects of the present disclosure will be provided below. It should be noted that, without conflict, the embodiments of the present disclosure and features in the embodiments may be combined with each other.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure, but the present disclosure may be practiced otherwise than as described herein; it will be apparent that the embodiments in the specification are only some, but not all, embodiments of the disclosure.
The data processor (Data Processing Unit, DPU) is a new generation of computing chips which are data-centric, I/O intensive, support infrastructure resource layer virtualization by adopting a software defined technology route, and have the advantages of improving the efficiency of the computing system, reducing the total ownership cost of the whole system, improving the data processing efficiency and reducing the performance loss of other computing chips.
A Service Mesh (Service Mesh) is an infrastructure layer in cloud services, focusing on achieving reliable delivery of Service requests between micro services, and providing traffic control layer operations such as Service discovery, load balancing, request routing, and rule configuration on the basis thereof. Currently, a plurality of proxy instances and application services on cloud server nodes are commonly used on a DPU to form a cloud native service grid, and enough proxy instances are deployed on the DPU to be capable of bearing all concurrent traffic on the cloud server nodes.
However, the number of deployed agent instances is static and cannot be dynamically increased or decreased with traffic demand, with the following problems: 1) When the service on the cloud server node suddenly increases, the quantity of the agent instances deployed on the DPU cannot meet the service request and service flow forwarding, so that the processor or the memory is insufficient, the processing time of a single data message is increased, the service request delay is increased, the jitter is increased, the service is unstable, or the service flow is discarded, so that a large quantity of retransmission is caused; 2) When traffic on cloud server nodes decreases, pre-deployed proxy instances are excessive, resulting in idle and wasted DPU processors, memory resources.
In view of this problem, embodiments of the present disclosure provide a proxy instance management method, which is described below in connection with specific embodiments.
Fig. 1 is a flowchart of a proxy instance management method provided by an embodiment of the present disclosure, where the method may be applied to an electronic device, and the method may be applied to a scenario of dynamic management of a proxy instance, where when a service on a cloud server node increases, the proxy instance is amplified to meet a service request and a service traffic forwarding requirement; when the traffic flow on the cloud server node is reduced, the proxy instance is reduced, so that idle and waste of the processor and memory resources are avoided. It can be appreciated that the agent instance management method provided by the embodiment of the present disclosure may also be applied in other scenarios.
The DPU is a heterogeneous network computing acceleration engine which works on cloud server nodes and provides high bandwidth and low latency for the cloud server nodes. The electronic device is configured on the DPU, and may be specifically an Auto-scaling unit or device (Auto Scaler).
The following describes a proxy instance management method shown in fig. 1, which includes the following steps:
s101, carrying out initial configuration on the agent instance based on preset configuration information.
In some optional embodiments, the user may preset some configuration information, and the electronic device initially configures the proxy instance based on the preset configuration information in response to the configuration information preset by the user. The preset configuration information comprises the initial number of agent instances, and the corresponding relation between the agent instances and the service containers, namely, each agent instance is responsible for processing the service requests in which service container or the service requests in which service container. As shown in fig. 2, a solid box "proxy instance" represents an initially configured proxy instance, a solid box "Service Pod" represents an initially configured Service container, two proxy instances are initially configured, and there are initially three Service containers, each of which can process a Service request in the three Service containers.
S102, receiving service request monitoring data sent by a control plane agent, wherein the service request monitoring data is obtained by the control plane agent from a service interface.
A control plane agent is deployed on the cloud server node in advance, and the control plane agent can acquire service request monitoring data from a service interface. The control plane agent sends the service request monitoring data to the electronic equipment, and the electronic equipment receives the service request monitoring data sent by the control plane agent, wherein the service request monitoring data is obtained by the control plane agent from the service interface. In some embodiments, the service request monitoring data includes at least one of: throughput data, retransmission rate, response duration.
As shown in fig. 2, since the Service grid control plane agent (control plane agent) synchronizes with the Service grid control plane, the Service grid control plane may acquire Service request monitoring data from a Service interface (Service API) for monitoring a plurality of Service containers on the cloud server node and obtaining the Service request monitoring data, and thus the control plane agent may acquire the Service request monitoring data in the Service interface. Further, the control plane agent sends service request monitoring data to the electronic device, and the electronic device receives the service request monitoring data sent by the control plane agent.
S103, obtaining the load value of the proxy instance.
As shown in fig. 2, the electronic device may obtain a load value of each proxy instance, where the load value may reflect a processor usage rate, a memory occupancy rate, and the like of each proxy instance.
And S104, managing the proxy instance based on the service request monitoring data or managing the proxy instance based on the load value of the proxy instance.
After receiving the service request monitoring data sent by the control plane proxy, the electronic device may manage the proxy instance according to the service request monitoring data. Or after obtaining the load value of the proxy instance, the electronic device may manage the proxy instance according to the load value of the proxy instance. The agent instance is managed, namely the agent instance is dynamically expanded or recovered, namely the number of the agent instance is increased or reduced, so that when the service on the cloud server node is increased, the agent instance is expanded, and the requirements of service request and service flow forwarding are met; when the traffic flow on the cloud server node is reduced, the proxy instance is reduced, so that idle and waste of the processor and memory resources are avoided.
According to the embodiment of the disclosure, the agent instance is initially configured based on preset configuration information, service request monitoring data sent by the control plane agent is received, the service request monitoring data are obtained by the control plane agent from the service interface, the load value of the agent instance is obtained, and the service request monitoring data are based on the obtained service request monitoring data
The service request monitoring data manages the proxy instance or manages the proxy instance based on the negative 5-load value of the proxy instance. The present disclosure is due to monitoring data or agents according to service requests
The case load condition dynamically manages the proxy case, improves the flexibility of proxy case management, and can realize the expansion of the proxy case when the service on the cloud server node is increased, so as to avoid the occurrence of traffic overload on the proxy case and meet the requirements of service request and service traffic forwarding;
when the traffic flow on the cloud server node is reduced, the proxy instance is reduced, so that idle and waste of the processor and 0 memory resources are avoided.
FIG. 3 is a flowchart of a proxy instance management method according to another embodiment of the present disclosure, as shown in FIG. 3
As shown, the method comprises the following steps:
s301, obtaining the corresponding relation between the proxy instance and the service request 5 according to the preset configuration information.
The electronic equipment can obtain the corresponding relation between the proxy instance and the service request according to the preset configuration information. An agent instance may process one service request, or may process multiple service requests, which is not limited herein. That is, the proxy instance and the service request may have a one-to-one relationship or a one-to-many relationship.
And 0S302, determining a target service request corresponding to the proxy instance from the corresponding relation.
After obtaining the correspondence, the electronic device may determine, from the correspondence, a target service request corresponding to each proxy instance.
S303, establishing connection between the proxy instance and the target service request.
5 after determining the target service request corresponding to each proxy instance, the electronic device will
Each proxy instance establishes a session connection with its corresponding target service request.
S304, receiving service request monitoring data sent by the control plane agent, wherein the service request monitoring data is obtained by the control plane agent from a service interface.
Specifically, the implementation process and principle of S304 and S102 are consistent, and will not be described herein.
S305, judging whether the service request monitoring data meets the amplification conditions of the agent instance.
After receiving the service request monitoring data sent by the control plane agent, the electronic equipment judges
Interrupting the service request monitoring data if the amplified condition of the proxy instance is met. In some embodiments, the amplification conditions of the proxy instance include that the throughput data of the proxy instance is less than a preset throughput
The amount threshold, the retransmission rate of the proxy instance being greater than a preset retransmission rate threshold, the response time period of the proxy instance being greater than a preset response time period threshold, etc., are not particularly limited.
In some embodiments, the service request monitoring data includes at least one of: throughput data, retransmission rate, response duration.
0, the service request monitoring data at least comprises throughput data, retransmission rate and response
The duration is not limited herein.
In some embodiments, S305 includes, but is not limited to S3051, S3052:
s3051, if the throughput data is smaller than a preset throughput threshold, or the retransmission rate is large
And if the preset retransmission rate threshold value or the response time length is larger than the preset response time length threshold value, the amplification condition of the 5-agent example is met.
S3052, if the throughput data is greater than or equal to the preset throughput threshold, the retransmission rate is less than or equal to the preset retransmission rate threshold, and the response time is less than or equal to the preset response time threshold, the amplification condition of the proxy instance is not satisfied.
S306, if the amplification conditions of the proxy instance are met, amplifying the proxy instance. And 0, if the electronic equipment judges that the service request monitoring data meets the amplification conditions of the proxy instance, amplifying the proxy instance, namely increasing the number of the proxy instance to avoid the occurrence of traffic overload on the proxy instance, thereby meeting the requirements of service request and service traffic forwarding.
S307, calculating the resource occupancy rate of the CPU and the memory of the proxy instance.
In this step, the electronic device calculates the 5 resource occupancy rates of the central processor and the memory of the proxy instance, so as to obtain the resource occupancy condition of the proxy instance.
S308, determining the load value of the proxy instance corresponding to the resource occupancy rate of the central processor and the memory of the proxy instance from the corresponding relation between the resource occupancy rate and the load value.
The electronic equipment stores the corresponding relation between the occupancy rate of the central processing unit and the memory and the load value, and can determine the current load value of the proxy instance corresponding to the occupancy rate of the central processing unit and the memory of the proxy instance from the corresponding relation between the occupancy rate of the central processing unit and the memory and the load value. For example, the load value corresponding to the occupancy rate 40% is 4, the load value corresponding to the occupancy rate 58% is 5.8, and the like, and this step is only to explain the corresponding relation between the occupancy rates of the central processing unit and the memory and the load values, but not to limit the corresponding relation between the occupancy rates of the central processing unit and the memory and the load values. The load values corresponding to the occupancy rates of 70% -75% are all 7.
It can be appreciated that the higher the resource occupancy, the more severe the resource occupancy, and the larger the load value.
S309, amplifying or reducing the proxy instance according to the magnitude relation between the load value of the proxy instance and a plurality of thresholds.
After determining the load value of the proxy instance, the electronic device may amplify or shrink the proxy instance according to a magnitude relationship between the load value of the proxy instance and a plurality of thresholds. When the load value is larger, amplifying the proxy instance to avoid the overload of the traffic on the proxy instance and meet the requirements of service request and traffic forwarding; when the load value is smaller, the proxy instance is reduced, so that idle and waste of the processor and memory resources are avoided.
According to the embodiment of the disclosure, the corresponding relation between the proxy instance and the service request is obtained according to the preset configuration information, the target service request corresponding to the proxy instance is determined from the corresponding relation, and the proxy instance and the target service request are connected. Further, receiving service request monitoring data sent by a control plane proxy, wherein the service request monitoring data is obtained by the control plane proxy from a service interface, judging whether the service request monitoring data meets the amplification conditions of a proxy instance, and amplifying the proxy instance if the service request monitoring data meets the amplification conditions of the proxy instance; or calculating the resource occupancy rate of the central processor and the memory of the proxy instance, determining the load value of the proxy instance corresponding to the resource occupancy rate of the central processor and the memory of the proxy instance from the corresponding relation between the resource occupancy rate and the load value, and further amplifying or reducing the proxy instance according to the magnitude relation between the load value of the proxy instance and a plurality of thresholds. And the judgment is carried out according to two different judgment bases, so that the agent instance is dynamically managed according to the judgment result, and the flexibility of the agent instance management is improved. When the service on the cloud server node is increased, the proxy instance can be amplified, so that the overload of the traffic on the proxy instance is avoided, and the requirements of service request and service traffic forwarding are met; when the traffic flow on the cloud server node is reduced, the proxy instance is reduced, so that idle and waste of the processor and memory resources are avoided.
Fig. 4 is a flowchart of a proxy instance management method according to another embodiment of the present disclosure, as shown in fig. 4, where the method includes the following steps:
s401, carrying out initial configuration on the agent instance based on preset configuration information.
Specifically, the implementation process and principle of S401 and S101 are identical, and will not be described herein.
S402, receiving service request monitoring data sent by a control plane agent, wherein the service request monitoring data is obtained by the control plane agent from a service interface.
Specifically, the implementation process and principle of S402 and S102 are consistent, and will not be described herein.
S403, judging whether the service request monitoring data meets the amplification conditions of the proxy instance, if yes, executing S407, otherwise executing S408.
After receiving the service request monitoring data sent by the control plane proxy, the electronic device may determine whether the service request monitoring data meets the amplification conditions of the proxy instance, and if the service request monitoring data meets the amplification conditions of the proxy instance, execute S407; if the service request monitoring data does not satisfy the augmentation condition of the proxy instance, S408 is performed.
S404, obtaining the load value of the proxy instance.
Specifically, the implementation process and principle of S404 and S103 are identical, and will not be described herein.
S405, judging whether the load value of the proxy instance is smaller than or equal to a preset first load value threshold, if yes, executing S409, otherwise executing S406.
After the load value of the proxy instance is obtained, the electronic equipment judges whether the load value of the proxy instance is smaller than or equal to a preset first load value threshold value. If the load value of the proxy instance is less than or equal to a preset first load value threshold, executing S409; if the load value of the proxy instance is greater than a preset first load value threshold, steps S406 and following S406 are performed.
S406, judging whether the load value of the agent instance is greater than or equal to a preset second load value threshold, if so, executing S407, otherwise, executing S408.
And if the load value of the proxy instance is greater than a preset first load value threshold, judging whether the load value of the proxy instance is greater than or equal to a preset second load value threshold. If the load value of the proxy instance is greater than or equal to a preset second load value threshold, executing S407; if the load value of the proxy instance is less than the preset second load value threshold, S408 is performed.
S407, amplifying the agent instance.
And if the load value of the proxy instance is larger than or equal to a preset second load value threshold, namely the load value is larger, amplifying the proxy instance. Or if the service request monitoring data meets the amplification conditions of the proxy instance, amplifying the proxy instance. Thereby avoiding the overload of the traffic on the proxy instance and meeting the requirements of service request and service traffic forwarding.
In some embodiments, S407 includes, but is not limited to, S4071, S4072, S4073:
s4071, acquiring configuration information of the newly added agent instance from the service grid control plane.
As shown in fig. 2, the electronic device (specifically, auto Scaler) may obtain configuration information of the newly added agent instance from the service grid control plane. Because the Service grid control plane agent (control plane agent) is synchronized with the Service grid control plane, the Service grid control plane can acquire the configuration information of the newly added agent instance from the Service interface (Service API) which is used for generating the configuration information of the newly added agent instance, so that the control plane agent can acquire the configuration information of the newly added agent instance in the Service interface.
S4072, determining a service request connected with the newly added proxy instance according to the configuration information of the newly added proxy instance.
After obtaining the configuration information of the newly added proxy instance, the electronic device may determine, according to the configuration information of the newly added proxy instance, a service request connected with the newly added proxy instance.
S4073, establishing connection between the newly added agent instance and the service request.
After determining a service request connected with the newly added proxy instance, the electronic device establishes a session connection between the newly added proxy instance and the service request.
S408, keeping the agent instance unchanged.
If the load value of the proxy instance is greater than a preset first load value threshold and the load value of the proxy instance is less than a preset second load value threshold, the number of proxy instances is determined
Remain unchanged. Or if the service request monitoring data does not meet the augmentation condition 5 of the proxy instance, the number of proxy instances is kept unchanged.
S409, the agent instance is reduced.
And if the load value of the proxy instance is smaller than or equal to a preset first load value threshold, reducing the proxy instance.
In some embodiments, the reducing the proxy instance includes: and disconnecting the proxy 0 agent instance from the service request, and recovering resources of the proxy instance.
Specifically, the electronic device disconnects the proxy instance from the service request, and recovers resources of the proxy instance, so that idle and waste of processor and memory resources are avoided.
The embodiment of the disclosure initially configures the proxy instance based on preset configuration information. 5 further, receiving service request monitoring data sent by the control plane agent, wherein the service request monitoring data comprises a service request information
The data measurement is obtained by the control plane proxy from the service interface, whether the service request monitoring data meet the amplification conditions of the proxy instance is judged, if yes, the proxy instance is amplified, and otherwise, the proxy instance is kept unchanged; or obtaining the load value of the proxy instance, and judging the proxy instance
Judging whether the load value of the 0 agent example is larger than or equal to a preset second load value threshold value or not according to whether the load value of the 0 agent example is smaller than or equal to a preset first load value threshold value or not, and further according to the judgment result
The magnitude relation between the load value of the proxy instance and a plurality of thresholds is used for amplifying the proxy instance, or the proxy instance is kept unchanged, or the proxy instance is reduced. Because a plurality of judgment bases are set, the agent instance is amplified according to the judgment result, or the agent instance is amplified
The agent instance is kept unchanged or reduced, the flexibility of agent instance management is improved, and 5, the traffic overload on the agent instance can be avoided, and the service request and the traffic transfer can not be met
The problem of demand can also be avoided, and the problem of idle and waste of processor and memory resources can be avoided.
Fig. 5 is a schematic structural diagram of an agent instance management device according to an embodiment of the present disclosure. The agent instance management apparatus may be the electronic device of the above embodiment, or the agent instance management apparatus may be a part or component in the electronic device. The proxy instance management apparatus provided by the embodiment of the present disclosure may execute the process flow provided by the proxy instance management method embodiment, as shown in fig. 5, the proxy instance management apparatus 50 includes: a configuration module 51, a receiving module 52, an acquisition module 53, and a management module 54; the configuration module 51 is configured to initially configure the proxy instance based on preset configuration information; the receiving module 52 is configured to receive service request monitoring data sent by a control plane agent, where the service request monitoring data is obtained by the control plane agent from a service interface; the obtaining module 53 is configured to obtain a load value of the proxy instance; the management module 54 is configured to manage the proxy instance based on the service request monitoring data, or manage the proxy instance based on a load value of the proxy instance.
Optionally, when the configuration module 51 performs initial configuration on the proxy instance based on preset configuration information, the configuration module is specifically configured to: obtaining a corresponding relation between the proxy instance and the service request according to the preset configuration information; determining a target service request corresponding to the proxy instance from the corresponding relation; and establishing connection between the proxy instance and the target service request.
Optionally, when the obtaining module 53 obtains the load value of the proxy instance, the obtaining module is specifically configured to: calculating the resource occupancy rate of a central processor and a memory of the proxy instance; and determining the load value of the proxy instance corresponding to the resource occupancy rate of the central processor and the memory of the proxy instance from the corresponding relation between the resource occupancy rate and the load value.
Optionally, when the management module 54 manages the proxy instance based on the service request monitoring data, the management module is specifically configured to: judging whether the service request monitoring data meets the amplification conditions of the proxy instance or not; if the amplification conditions of the proxy instance are met, amplifying the proxy instance; the management module 54 is specifically configured to, when managing the proxy instance based on the load value of the proxy instance: and amplifying or reducing the proxy instance according to the magnitude relation between the load value of the proxy instance and a plurality of thresholds.
Optionally, the service request monitoring data includes at least one of: throughput data, retransmission rate, and response time;
the management module 54 is specifically configured to, when determining whether the service request monitoring data meets the amplification condition of the proxy instance: if the throughput data is smaller than a preset throughput threshold, or the retransmission rate is larger than a preset retransmission rate threshold, or the response time is longer than a preset response time threshold, the amplification condition of the proxy instance is met; if the throughput data is greater than or equal to the preset throughput threshold, the retransmission rate is less than or equal to the preset retransmission rate threshold, and the response time is less than or equal to the preset response time threshold, the amplification condition of the proxy instance is not satisfied.
Optionally, the management module 54 is specifically configured to, when amplifying or reducing the proxy instance according to the magnitude relation between the load value of the proxy instance and the multiple thresholds: if the load value of the proxy instance is smaller than or equal to a preset first load value threshold, the proxy instance is reduced; if the load value of the proxy instance is greater than or equal to a preset second load value threshold, amplifying the proxy instance; and if the load value of the proxy instance is larger than the preset first load value threshold and smaller than the preset second load value threshold, keeping the proxy instance unchanged.
Optionally, when the management module 54 performs reduction on the proxy instance, the method specifically is used for: disconnecting the proxy instance from the service request, and recovering resources of the proxy instance; the management module 54 is specifically configured to, when amplifying the agent instance: acquiring configuration information of a newly added agent instance from a service grid control plane; determining a service request connected with the newly added proxy instance according to the configuration information of the newly added proxy instance; and establishing connection between the newly added proxy instance and the service request.
The agent instance management device of the embodiment shown in fig. 5 may be used to implement the technical solution of the above method embodiment, and its implementation principle and technical effects are similar, and are not described herein again.
Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the disclosure. The electronic device may be a cloud server node or a data processor. The electronic device provided in the embodiment of the present disclosure may execute the processing flow provided in the embodiment of the proxy instance management method, as shown in fig. 6, the electronic device 60 includes: a memory 61, a processor 62, computer programs and a communication interface 63; wherein the computer program is stored in the memory 61 and configured to be executed by the processor 62 for the agent instance management method as described above.
In addition, the embodiment of the present disclosure also provides a computer-readable storage medium having stored thereon a computer program that is executed by a processor to implement the agent instance management method described in the above embodiment.
Furthermore, the disclosed embodiments also provide a computer program product comprising a computer program or instructions which, when executed by a processor, implements the agent instance management method as described above.
It should be noted that the computer readable medium described in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.
In some implementations, the clients, servers may communicate using any currently known or future developed network protocol, such as HTTP (HyperText Transfer Protocol ), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the internet (e.g., the internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed networks.
The computer readable medium may be contained in the electronic device; or may exist alone without being incorporated into the electronic device.
The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to:
initial configuration is carried out on the agent instance based on preset configuration information;
receiving service request monitoring data sent by a control plane agent, wherein the service request monitoring data is obtained by the control plane agent from a service interface;
acquiring a load value of an agent instance;
and managing the proxy instance based on the service request monitoring data or managing the proxy instance based on the load value of the proxy instance.
In addition, the electronic device may also perform other steps in the proxy instance management method as described above.
Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, including, but not limited to, an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present disclosure may be implemented by means of software, or may be implemented by means of hardware. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.
The functions described above herein may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Application Specific Standard Product (ASSP), a system on a chip (SOC), a Complex Programmable Logic Device (CPLD), and the like.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
It should be noted that in this document, relational terms such as "first" and "second" and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing is merely a specific embodiment of the disclosure to enable one skilled in the art to understand or practice the disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown and described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method for managing an agent instance, comprising:
initial configuration is carried out on the agent instance based on preset configuration information;
receiving service request monitoring data sent by a control plane agent, wherein the service request monitoring data is obtained by the control plane agent from a service interface;
acquiring a load value of an agent instance;
and managing the proxy instance based on the service request monitoring data or managing the proxy instance based on the load value of the proxy instance.
2. The method of claim 1, wherein the initially configuring the proxy instance based on the preset configuration information comprises:
obtaining a corresponding relation between the proxy instance and the service request according to the preset configuration information;
determining a target service request corresponding to the proxy instance from the corresponding relation;
and establishing connection between the proxy instance and the target service request.
3. The method of claim 1, wherein the obtaining the load value of the proxy instance comprises:
calculating the resource occupancy rate of a central processor and a memory of the proxy instance;
and determining the load value of the proxy instance corresponding to the resource occupancy rate of the central processor and the memory of the proxy instance from the corresponding relation between the resource occupancy rate and the load value.
4. The method of claim 1, wherein managing agent instances based on the service request monitoring data comprises:
judging whether the service request monitoring data meets the amplification conditions of the proxy instance or not;
if the amplification conditions of the proxy instance are met, amplifying the proxy instance;
the managing the proxy instance based on the load value of the proxy instance comprises the following steps:
and amplifying or reducing the proxy instance according to the magnitude relation between the load value of the proxy instance and a plurality of thresholds.
5. The method of claim 4, wherein the service request monitoring data comprises at least one of:
throughput data, retransmission rate, and response time;
the judging whether the service request monitoring data meets the amplification conditions of the proxy instance comprises the following steps:
if the throughput data is smaller than a preset throughput threshold, or the retransmission rate is larger than a preset retransmission rate threshold, or the response time is longer than a preset response time threshold, the amplification condition of the proxy instance is met;
if the throughput data is greater than or equal to the preset throughput threshold, the retransmission rate is less than or equal to the preset retransmission rate threshold, and the response time is less than or equal to the preset response time threshold, the amplification condition of the proxy instance is not satisfied.
6. The method of claim 4, wherein the expanding or shrinking the proxy instance according to the magnitude relationship between the load value of the proxy instance and the plurality of thresholds comprises:
if the load value of the proxy instance is smaller than or equal to a preset first load value threshold, the proxy instance is reduced;
if the load value of the proxy instance is greater than or equal to a preset second load value threshold, amplifying the proxy instance;
and if the load value of the proxy instance is larger than the preset first load value threshold and smaller than the preset second load value threshold, keeping the proxy instance unchanged.
7. The method of claim 6, wherein the reducing the proxy instance comprises:
disconnecting the proxy instance from the service request, and recovering resources of the proxy instance;
the amplifying the agent instance comprises the following steps:
acquiring configuration information of a newly added agent instance from a service grid control plane;
determining a service request connected with the newly added proxy instance according to the configuration information of the newly added proxy instance;
and establishing connection between the newly added proxy instance and the service request.
8. An agent instance management apparatus, comprising:
the configuration module is used for carrying out initial configuration on the agent instance based on preset configuration information;
the receiving module is used for receiving service request monitoring data sent by the control plane agent, wherein the service request monitoring data is obtained by the control plane agent from a service interface;
the acquisition module is used for acquiring the load value of the proxy instance;
and the management module is used for managing the proxy instance based on the service request monitoring data or managing the proxy instance based on the load value of the proxy instance.
9. An electronic device, comprising:
a memory;
a processor; and
a computer program;
wherein the computer program is stored in the memory and configured to be executed by the processor to implement the method of any one of claims 1-7.
10. A computer readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, implements the method according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211617443.6A CN116232884A (en) | 2022-12-15 | 2022-12-15 | Proxy instance management method, device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211617443.6A CN116232884A (en) | 2022-12-15 | 2022-12-15 | Proxy instance management method, device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116232884A true CN116232884A (en) | 2023-06-06 |
Family
ID=86572011
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211617443.6A Pending CN116232884A (en) | 2022-12-15 | 2022-12-15 | Proxy instance management method, device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116232884A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116599965A (en) * | 2023-07-18 | 2023-08-15 | 中移(苏州)软件技术有限公司 | Communication method, communication device, electronic apparatus, and readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112433845A (en) * | 2020-10-29 | 2021-03-02 | 苏州浪潮智能科技有限公司 | HBase service management method, device, equipment and readable medium |
| CN114138467A (en) * | 2021-11-12 | 2022-03-04 | 苏州浪潮智能科技有限公司 | Automatic capacity adjustment system, method, computer device, and storage medium |
| CN114385353A (en) * | 2021-12-23 | 2022-04-22 | 中国电信股份有限公司 | Resource scheduling method and device, electronic equipment and storage medium |
-
2022
- 2022-12-15 CN CN202211617443.6A patent/CN116232884A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112433845A (en) * | 2020-10-29 | 2021-03-02 | 苏州浪潮智能科技有限公司 | HBase service management method, device, equipment and readable medium |
| CN114138467A (en) * | 2021-11-12 | 2022-03-04 | 苏州浪潮智能科技有限公司 | Automatic capacity adjustment system, method, computer device, and storage medium |
| CN114385353A (en) * | 2021-12-23 | 2022-04-22 | 中国电信股份有限公司 | Resource scheduling method and device, electronic equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116599965A (en) * | 2023-07-18 | 2023-08-15 | 中移(苏州)软件技术有限公司 | Communication method, communication device, electronic apparatus, and readable storage medium |
| CN116599965B (en) * | 2023-07-18 | 2024-01-30 | 中移(苏州)软件技术有限公司 | Communication method, communication device, electronic apparatus, and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3637733B1 (en) | Load balancing engine, client, distributed computing system, and load balancing method | |
| CN108353067B (en) | Method, system and related equipment for realizing capability openness | |
| CN110958281B (en) | Data transmission method and communication device based on Internet of things | |
| CN111787069A (en) | Method, device and equipment for processing service access request and computer storage medium | |
| CN113115272A (en) | Service redirection method and device | |
| CN115883655B (en) | Service request processing method and device, electronic equipment and storage medium | |
| KR101773593B1 (en) | Mobile fog computing system for performing multi-agent based code offloading and method thereof | |
| US10178033B2 (en) | System and method for efficient traffic shaping and quota enforcement in a cluster environment | |
| Teranishi et al. | Dynamic data flow processing in edge computing environments | |
| CN115834708A (en) | Load balancing method, device, equipment and computer readable storage medium | |
| CN105635083A (en) | Service processing method and service processing system based on server and client architecture | |
| CN116232884A (en) | Proxy instance management method, device, electronic equipment and storage medium | |
| CN114365107A (en) | Network-based media processing (NBMP) workflow management controlled by 5G real-time uplink streaming framework (plus) | |
| CN106790354B (en) | Communication method and device for preventing data congestion | |
| CN104639557A (en) | Method and system for establishing PCEP (Path Computation Element Communication Protocol) session and equipment | |
| CN116886496A (en) | DPU-based data processing method, device, equipment and readable storage medium | |
| CN115277504B (en) | Network traffic monitoring method, device and system | |
| CN111049915A (en) | Message queue agent grid under container cloud and method | |
| US20100054195A1 (en) | Efficient Deallocation of Network Resources Based on Network Node Location Extrapolation | |
| CN115396494A (en) | Real-time monitoring method and system based on stream computing | |
| CN110753043B (en) | Communication method, device, server and medium | |
| US10742499B2 (en) | Distributed dynamic sizing and load self-management for a relay infrastructure | |
| US8989184B2 (en) | Message relay apparatus and method | |
| KR20220053383A (en) | Interworking support device and interworking support method for nf service | |
| CN113472565B (en) | Method, apparatus, device and computer readable medium for expanding server function |
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 |